Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[QUESTION] Why does nopt only work with cli args? #63

Open
tkrugg opened this issue May 8, 2016 · 0 comments
Open

[QUESTION] Why does nopt only work with cli args? #63

tkrugg opened this issue May 8, 2016 · 0 comments
Labels
Question further information is requested

Comments

@tkrugg
Copy link

tkrugg commented May 8, 2016

It makes sense to me that if you have a package that takes an options = {...} object as a parameter, you'd want the same level of validation and error handeling than the one you'd have on CLI args.
@darcyclarke darcyclarke changed the title Why does nopt only work with cli args? [QUESTION] Why does nopt only work with cli args? Jul 28, 2022
@darcyclarke darcyclarke added the Question further information is requested label Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Question further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@darcyclarke @tkrugg