Fails as cargo subcommand

[dspicher]

When invoked as a subcommand, cargo sort-ck fails because of how cargo passes on the command name as an argument:

"When Cargo invokes a custom subcommand, the first argument to the subcommand will be the filename of the custom subcommand, as usual. The second argument will be the subcommand name itself. For example, the second argument would be ${command} when invoking cargo-${command}. Any additional arguments on the command line will be forwarded unchanged."

https://doc.rust-lang.org/cargo/reference/external-tools.html#custom-subcommands

╰─$ cargo sort-ck                                                                                                                                                                                     101 ↵
Failure: No file found at: sort-ck/Cargo.toml

Is there a way to make the arguments to cargo-sort-ck consistent with how cargo passes them to subcommands?

[DevinR528]

First thank you for your interest.

Yea I was hoping I could get this to work when I first wrote this. I filed an issue with the cargo repo because every other crate that works as a subcommand seems to be doing the same things as this crate, I will keep investigating.

[DevinR528]

This commit if your curious fixes issue #4. Hope that works if you update your cargo-sort-ck version you should be good to go I published a new release.

[dspicher]

Just tested it, confirmed fixed. Thanks a lot for the quick response!!

[dspicher]

And thanks for the shoutout on the REAMDE :))