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

Define a good command line interface #4

Open
apmcleod opened this issue Jun 17, 2022 · 0 comments
Open

Define a good command line interface #4

apmcleod opened this issue Jun 17, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@apmcleod
Copy link

That's a general problem that we need to discuss and solve together. Does it even make sense to allow for arbitrary pipelines using the command line?

My suggestion would be, instead, to offer a well-defined set of commands such as dimcat bigrams and define the possible pipelines for it. The various combinations of groupers and slicers could then be distributed between

  • general arguments available for all commands (such as Corpus grouper) and
  • specific arguments share between those commands where they apply.

P.S.: Not even sure argparse is actually able to capture the difference in order in your example.

Originally posted by @johentsch in #1 (comment)

@apmcleod apmcleod added the enhancement New feature or request label Jun 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant