Closed laipz8200 closed 3 days ago
Note: And the change in this PR is not effective at the moment, which surely will cause many changes in future.
Note: And the change in this PR is not effective at the moment, which surely will cause many changes in future.
Sure, it's currently for internal use only.
And be careful when use Ruff's formatter and linter together. Some rules may be conflict.
And be careful when use Ruff's formatter and linter together. Some rules may be conflict.
Thanks for the reminder! We’ll introduce the formatter only when we’re ready, or would you be willing to help us check the rules?
I would prefer apply E and W rules of Ruff linters first ( https://docs.astral.sh/ruff/rules/#pycodestyle-e-w), if you guys are ready to brace a big change in multiple files for one time. Many of them are auto-fixable and help code formatting.
@bowenliang123 Great idea! We also want to apply some currently ignored rules (like F812 and F841). Maybe we will create a list and process them one by one.
No problem~ SGTM.
Description
This change is in preparation for the future introduction of the Ruff formatter. For now, we will not require the use of any formatter.
Fixes # (issue)
Type of Change
Please delete options that are not relevant.
How Has This Been Tested?
Suggested Checklist:
dev/reformat
(backend) andcd web && npx lint-staged
(frontend) to appease the lint godsoptional
I have made corresponding changes to the documentationoptional
I have added tests that prove my fix is effective or that my feature worksoptional
New and existing unit tests pass locally with my changes