Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
took the functionality of the third party subcommand from the list_co…
…mmands function (#15075) Hey there, I just moved the functionality of the third-party subcommand from the [list_commands](https://github.com/rust-lang/cargo/blob/master/src/bin/cargo/main.rs#L184) function to another new function by the name of third_party_subcommand name and called that function in the list_commands function. From my understanding regarding the third-party subcommand from this [tracking issue](#14520), following points should be performed. - The code that gathers third-party subcommands in list_commands should be moved into a separate function that I did. - This new function will be called both by list_commands and the code for adding subcommand completions. Although I called the function in the list_commands but didn't understand the second point. - Test the change that I made in the first place but it gave me this error: ![carbon (68)](https://github.com/user-attachments/assets/fb4c5a55-ea4b-4d22-b187-c2a417f5128d) <!-- Thanks for submitting a pull request 🎉! Here are some tips for you: * If this is your first contribution, read "Cargo Contribution Guide" first: https://doc.crates.io/contrib/ * Run `cargo fmt --all` to format your code changes. * Small commits and pull requests are always preferable and easy to review. * If your idea is large and needs feedback from the community, read how: https://doc.crates.io/contrib/process/#working-on-large-features * Cargo takes care of compatibility. Read our design principles: https://doc.crates.io/contrib/design.html * When changing help text of cargo commands, follow the steps to generate docs: https://github.com/rust-lang/cargo/tree/master/src/doc#building-the-man-pages * If your PR is not finished, set it as "draft" PR or add "WIP" in its title. * It's ok to use the CI resources to test your PR, but please don't abuse them. ### What does this PR try to resolve? Explain the motivation behind this change. A clear overview along with an in-depth explanation are helpful. You can use `Fixes #<issue number>` to associate this PR to an existing issue. ### How should we test and review this PR? Demonstrate how you test this change and guide reviewers through your PR. With a smooth review process, a pull request usually gets reviewed quicker. If you don't know how to write and run your tests, please read the guide: https://doc.crates.io/contrib/tests ### Additional information Other information you want to mention in this PR, such as prior arts, future extensions, an unresolved problem, or a TODO list. -->
- Loading branch information