-
Notifications
You must be signed in to change notification settings - Fork 71
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
Provide command-line interface #109
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution! Please also check the output of the travis run and fix the issues pre-commit
mentioned. You can run make install-hooks
to make sure those hooks will be run when you commit code.
requirements-dev.txt
Outdated
@@ -1,3 +1,6 @@ | |||
httpretty | |||
mock | |||
pytest | |||
jsonschema | |||
pyyaml | |||
six |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These requirements are already listed in setup.py
, no need to add them here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apparently, the correct way is to put a line with a single .
so that pip install -r requirements-dev.txt
will automatically look in setup.py
as well. I've pushed a new version reflecting this.
f22cae4
to
0b1cf49
Compare
This makes it possible to call the script as follows: python -m swagger_spec_validator "http://petstore.swagger.io/v2/swagger.json"
See #105 which includes some basic tests, an entrypoint, documentation, and processing of the raised exception to print the message rather than dumping a traceback. |
Makes the following possible:
python -m swagger_spec_validator "http://petstore.swagger.io/v2/swagger.json"