Skip to content
This repository was archived by the owner on Feb 13, 2024. It is now read-only.

Suggestions for features to define #16

Open
10 tasks
karfau opened this issue Jan 10, 2020 · 0 comments
Open
10 tasks

Suggestions for features to define #16

karfau opened this issue Jan 10, 2020 · 0 comments

Comments

@karfau
Copy link
Owner

karfau commented Jan 10, 2020

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.

  • parsing of arguments
  • stop at first positional
  • 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
karfau added a commit that referenced this issue Jan 31, 2020
`{"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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant