New Argument Parser Support #931
Draft
Conversation
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
This commit adds support for a new argument parser, using Unix/Linux convention and backed by arweave_config. The main idea is to set arweave from command line with the same parameters than environment or configuration file. Long and short arguments are supported, both of them are defined in the specifications (at this time, mostly stored in arweave_config_parameters). see: ArweaveTeam/arweave-dev#971
humaite
force-pushed
the
humaite/971-new-command-line-parser
branch
from
ada84f6 to
548d7af
Compare
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 commit adds support for a new argument parser, using Unix/Linux convention and backed by arweave_config. The main idea is to set arweave from command line with the same parameters than environment or configuration file.
Long and short arguments are supported, both of them are defined in the specifications (at this time, mostly stored in
arweave_config_parameters).
see: https://github.com/ArweaveTeam/arweave-dev/issues/971