Repository navigation
feat: accept --networks as an alias of --network - #29
Merged
Merged
Conversation
miguelmota
approved these changes
Oct 6, 2026
Member
|
LGTM! |
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.
This PR prevents my own idiocy...
--networksnow works anywhere--networkdoes (run,dry-run,etherscan). Typing the plural is too easy.mapAliasesinsrc/index.tsrewrites aliased long flags in argv before commander parses them, covering both--networks xand--networks=x. Commander 11 can't give a long option a second name, so this is the smallest way to do it. Adding another alias is one entry inOPTION_ALIASES.Things to watch:
--helponly shows--network.--networksgets rewritten too.