docs: no subcommands, no worries#47
Merged
bcoe merged 1 commit intopkgjs:mainfrom Jan 25, 2022
Merged
Conversation
Eomm
approved these changes
Jan 24, 2022
bcoe
approved these changes
Jan 24, 2022
Collaborator
bcoe
left a comment
bcoe
left a comment
There was a problem hiding this comment.
It complicates the heck out of the design to support subcommands, I think you should reach for yargs, commander, etc., if you need parsing this complex -- or build something on top of parseargs.
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
3 participants
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.
We have lots of problems, but lack of subcommands is not one of them. 🤣
Support for subcommands has not come up in issues or discussion, so not worth continuing to qualify in README. Just saying no covers it fine.