Add documentation on 'noBacktrack' preference #300
Conversation
This file contains 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
|
@HuwCampbell this should avoid a repeat of someone like me creating a (non-) issue like #298 in the future :-) |
Subcommand parsers are often disjoint, meaning that if one fails to parse after the command name then all others (having distinct command names) will also fail to parse. When the 'noBacktrack' preference is not set but 'showHelpOnError' is this leads to the help for the top-level parser being shown instead of the help for the failing subcommand. A note has been added to the Haddock docs for the 'noBacktrack' option to make this clear.
sseefried
force-pushed
the
PR-1-add-docs-on-noBacktrack-and-showHelp
branch
from
e37c20a
to
08edd73
Compare
sseefried
changed the title
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.
Subcommand parsers are often disjoint, meaning that if one fails
to parse after the command name then all others (having distinct
command names) will also fail to parse. When the 'noBacktrack'
preference is not set but 'showHelpOnError' is this leads to
the help for the top-level parser being shown instead of the
help for the failing subcommand.
A note has been added to the Haddock docs for the 'noBacktrack'
option to make this clear.