-
Notifications
You must be signed in to change notification settings - Fork 9
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
CLI Design for OpenAPI parser #17
Comments
Setting a default for output file name would good, so it's not a mandatory param. Also short alternatives like "-i" for --openapi-doc-input and "-o" for --hydradoc-output would be handy. |
Please take a look at https://github.com/de-sh/hydra-openapi-parser/tree/cli
I think we can make use of simple CLI arguments for that. I also learned that in hydrus, I'll make a PR if we can solve the issue with CLI... |
I liked the smaller parameters, looks like it has the basic func. I find summing this up important for us to close #13, so we can add to the readme something like:
Guess we need it to link with the package adding "entry_points" at the setup.py so we can use it as hydra-openapi-parser and have some documentation to use it. |
#18 merged |
I'm submitting a
Current Behaviour:
Currently the openapi-parser library is imported as a python package and that is about all the facilities it provides a user. A CLI would allow for a user to utilise this as a standalone app for purposes that might be divergent from what this was originally meant to be.
Expected Behaviour:
The CLI should allow for the user to use the command hydra-openapi-parser to generate a hydraDoc. This could be as simple as:
Do you want to work on this issue?
Yes, but I would need help with designing the CLI
The text was updated successfully, but these errors were encountered: