We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
symbex --undocumented --check
The --check option would cause symbex to return a non-zero exit code if it finds any matches.
--check
symbex
In this way you could use symbex in CI such as GitHub Actions to fail tests if any code is added which is missing types or docstrings:
symbex --undocumented --check symbex --untype --check
The text was updated successfully, but these errors were encountered:
Inspired by cog --check and black --check and various other linters.
cog --check
black --check
Sorry, something went wrong.
black . --check returns 1 on errors so I'll use 1 (I thought maybe it should be 2 or something else).
black . --check
1
2
It's going to return 0 output, unless you pass --count in which case it will display the count.
--count
Or pass --check -s to see the signatures.
--check -s
2b102a9
symbex --check option, closes #35
ef0d6f3
Release 1.1
f71707d
Refs #33, #34, #35
No branches or pull requests
The
--check
option would causesymbex
to return a non-zero exit code if it finds any matches.In this way you could use
symbex
in CI such as GitHub Actions to fail tests if any code is added which is missing types or docstrings:The text was updated successfully, but these errors were encountered: