-
Notifications
You must be signed in to change notification settings - Fork 91
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
Use code formatter on source #157
Comments
You might start using super-linter in a test workflow.
That is at least validating newly touched files using Black. It is not auto-reformatting. That's something you would to cover through your IDE the best (e.g. VSCode, ms-python.black-formatter extension). You may dive into adding a .devcontainer folder with respective files (Dockerfile, devcontainer.json, ...) to add a Python-based Dev Container to have always a working environment at hand which is handy if you switch to another device. You just need docker. VSCode automatically starts the container up and you can directly develop in there. All this is coming with some work, but worth it. |
Njj |
Thanks @kurtmckee and @waketzheng for your contributions on this. Unfortunately I didn't notice the PR for |
No worries, and no hard feelings! Thanks for your work on idna! 🥳 |
Review using
black
,ruff
formatter, or similar to consistently format codebase. Note thatidna-data make-libdata
needs to generate code fragments that conform with this style.The text was updated successfully, but these errors were encountered: