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

Implement test #52

Open
GrayJack opened this issue Sep 27, 2019 · 2 comments
Open

Implement test #52

GrayJack opened this issue Sep 27, 2019 · 2 comments
Labels
A-tool Area: Binary tool C-tracking-issue Category: A tracking issue for an feature. Hacktoberfest Hacktoberfest

Comments

@GrayJack
Copy link
Owner

No description provided.

@halfbro
Copy link

halfbro commented Oct 31, 2019

I'm interested in implementing this

What do you think should be done about some of the test syntaxes? It seems like clap is not a great fit for doing some of the parsing that test expects, like =, ==, etc.

Also, how should I approach handling calling test using [ vs. test?

@GrayJack
Copy link
Owner Author

GrayJack commented Nov 1, 2019

Also, how should I approach handling calling test using [ vs. test?

Hmm no sure how to handle this, but you can just accept test at first

What do you think should be done about some of the test syntaxes? It seems like clap is not a great fit for doing some of the parsing that test expects, like =, ==, etc.

Clap can handle it with a value that can be multiple EXPRESSION, get it's value and parse it.
That is my guess

@GrayJack GrayJack added C-tracking-issue Category: A tracking issue for an feature. A-tool Area: Binary tool labels Dec 28, 2020
@GrayJack GrayJack added the Hacktoberfest Hacktoberfest label Oct 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-tool Area: Binary tool C-tracking-issue Category: A tracking issue for an feature. Hacktoberfest Hacktoberfest
Projects
None yet
Development

No branches or pull requests

2 participants