You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 13, 2024. It is now read-only.
I'm collectiong rough ideas here of features to describe once I finished the current parsers (or maybe some from #2). They would then be added to each pkg/features.json in one go.
also talk about -- which is a common convention in unix
the topic "interspersed arguments", the possibility to mix options and positional arguments, seems to be related.
slicing of argv (mandatory vs default vs configurable ...)
help/usage output
generated from configuration?
quite some options out there
automatic/reserverd flag(s)
checking keys from process.env (e.g. based on prefix, or configured per option)
checking config file(s) for options
Paradigms: Singelton/global state; functional; Class instance;...?
options.syntax:-o=value
options.syntax:grouping of single letter aliases
options.syntax.default-value: default value for options not passed (has been specified for dashdash, because I confused it with options.types.default-string)
Later (or might not happen if I don't need it, but open for PRs although would prefer other features first.)
compatible option formats (I think I have seen similarities/compatibility goals between some libs)
support for (sub)command(s)
seems to be quite a big scope and the differences might be huge
I don't need it for runex currently
The text was updated successfully, but these errors were encountered:
`{"features":24,"unspecified":9,"specified":4,"verified":11,"checks":26}`
Already specified `options.syntax.default-value` (not part of schema yet,
not included in the count above)
#16
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm collectiong rough ideas here of features to describe once I finished the current parsers (or maybe some from #2). They would then be added to each
pkg/features.json
in one go.--
which is a common convention in unixoptions.syntax
:-o=value
options.syntax
:grouping of single letter aliasesoptions.syntax.default-value
: default value for options not passed (has been specified fordashdash
, because I confused it withoptions.types.default-string
)Later (or might not happen if I don't need it, but open for PRs although would prefer other features first.)
runex
currentlyThe text was updated successfully, but these errors were encountered: