[Docs]: Document and test boolean options consuming true/false strings #74
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
ljharb
reviewed
Jan 22, 2025
Fixes minimistjs#64 Co-authored-by: Jordan Harband <[email protected]>
shadowspawn
force-pushed
the
document-true-false-consumption
branch
from
5f82e2e to
11303eb
Compare
ljharb
approved these changes
Jan 22, 2025
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.
An undocumented feature is that explicit boolean options consume arguments which are the strings
trueorfalse. This leads to surprise when people discover the behaviour. Leaving aside whether the behaviour is a good idea, at least document it!Fixes #64