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

Move CLI parser to its own component #700

Open
tomadamatkinson opened this issue May 11, 2023 · 3 comments
Open

Move CLI parser to its own component #700

tomadamatkinson opened this issue May 11, 2023 · 3 comments
Labels
framework This is relevant to the framework v2.0 Work relating to the framework v2.0 project

Comments

@tomadamatkinson
Copy link
Collaborator

The CLI parser is self contained and is the sole reason why we have the cli11 third party. This can be directly moved to its own component

@tomadamatkinson tomadamatkinson added framework This is relevant to the framework v2.0 Work relating to the framework v2.0 project labels May 11, 2023
@tomadamatkinson tomadamatkinson added this to the Framework v2.0 milestone May 11, 2023
@mjbmon
Copy link

mjbmon commented Feb 10, 2024

I strongly support this, but then you need to document in the build instructions that cli11 is a dependency that needs to be installed.

@SaschaWillems
Copy link
Collaborator

Do we still want to do this? Imo the current CLI parser works just fine.

@marty-johnson59
Copy link
Contributor

@tomadamatkinson, can we close this or is there more to do?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
framework This is relevant to the framework v2.0 Work relating to the framework v2.0 project
Projects
None yet
Development

No branches or pull requests

4 participants