We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Something I discovered while working on #64 was that some of the code snippets were not compliant with the code style guidelines.
After looking for a solution, I came across blacken-docs, which turned out to be extremely useful.
The main idea behind this new feature would be to add this doc style checker to our current style tests via pre-commit.
Blacken-docs: https://github.com/asottile/blacken-docs/
The text was updated successfully, but these errors were encountered:
⚠️ Notice some of our examples are non-style compliant on purpose
This is done to educate others on what to do and avoid. As long as blacken-docs can ignore these files, we can implement this feature.
blacken-docs
Sorry, something went wrong.
@jorgepiloto I will implement it for PyAEDT. It should be even easier, because in this repo we shouldn't ignore any code samples.
Working on this. I will also implement pre-commit.ci in this task if it's okay with you all.
RobPasMue
Successfully merging a pull request may close this issue.
Description of the feature
Something I discovered while working on #64 was that some of the code snippets were not compliant with the code style guidelines.
After looking for a solution, I came across blacken-docs, which turned out to be extremely useful.
Steps for implementing the feature
The main idea behind this new feature would be to add this doc style checker to our current style tests via pre-commit.
Useful links and references
Blacken-docs: https://github.com/asottile/blacken-docs/
The text was updated successfully, but these errors were encountered: