Repository navigation
Conversation
Collaborator
|
Are there any issues with structopt? It seems to work fine, it parses arguments, maybe it just doesn't need updates. |
Author
|
Sure, I'm not suggesting there is anything wrong with structopt, but there are still good reasons to switch:
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
structoptcrate is obsolete. Its functionality has been integrated intoclapversions 3 and newer. The last actual release was in 2021; v0.3.26 in 2022 only added a deprecation notice to the docs.The
structoptcrate has also been officially marked as unmaintained a few months ago: https://rustsec.org/advisories/RUSTSEC-2022-0104.html.This PR migrates from
structoptto clap v4.(The text above is derived from https://bugzilla.redhat.com/show_bug.cgi?id=2554591)