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.

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

Suggestion: use Deno's std/flags to parse arguments #71

Open
1 of 3 tasks
guifromrio opened this issue Mar 8, 2020 · 1 comment
Open
1 of 3 tasks

Suggestion: use Deno's std/flags to parse arguments #71

guifromrio opened this issue Mar 8, 2020 · 1 comment

Comments

@guifromrio
Copy link
Contributor

Issue Type

  • Bug Report
  • Feature Request
  • Other

Info

I see this project currently uses mri (https://www.npmjs.com/package/mri) to parse the arguments.

I suggest we discuss using the standard flags (https://deno.land/std/flags/) module when running on Deno so it behaves consistently with other cli's created in deno.

@egoist
Copy link
Collaborator

egoist commented May 14, 2020

But that would make CAC behave differently on different platform.

Anyways I plan to write our own cli parser instead of using mri, so I can try to make it as close to Deno's as possible.

Currently the only difference I noticed is that Deno parses -n5 to {n:5} while we parse it to {n:true,5:true}.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants