-
Notifications
You must be signed in to change notification settings - Fork 0
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
Solving lint rule issues #1403
Comments
It does. If you ever open
+1, and have CICD to check for those, like the Workflow team is doing. @mcastril something that could be included for the September extraordinary team meeting agenda, IMO. We don't need to fix all at one, but maybe during August or December, when things are calmer, we could fix a bunch, and then the next chance we have we fix a little more... Thanks Luiggi! |
In GitLab by @dbeltrankyl on Aug 28, 2024, 10:30 Thanks Luiggi, The IDE (pycharm) can solve a few of these issues with some inbuilt tools, I've used it a couple of times. I usually don't use it in a merge request because it makes modifications to all code and complicates the code review. Maybe we should start by using that tool in a separate merge request, merge it, and we can include a procedure to run it in each new merge requests as it will only fix the new code added and doesn't complicate the code review |
In GitLab by @dbeltrankyl on Aug 28, 2024, 15:15 mentioned in merge request autosubmit4-config-parser!9 |
In GitLab by @LuiggiTenorioK on Aug 28, 2024, 15:41
+1
Indeed, Ruff also can fix some of them "safely". I prefer to use Ruff since it also includes the code formatter and rules from other linters. Also, it is used in other projects in ES (like the one presented by Bruno and Aina) and works on different IDEs (VSCode and Pycharm as well). |
In GitLab by @LuiggiTenorioK on Sep 2, 2024, 14:12 mentioned in issue autosubmit-api#87 |
This is something we can enlist Erick to help with. 👍 |
In GitLab by @LuiggiTenorioK on Aug 27, 2024, 14:49
The current source code of Autosubmit has many underlying issues that can be easily detected by linters.
Just running Ruff, we have the following rules that are violated:
It will be nice to solve them to prevent future bugs and keep tracking them in future releases as part of our development process.
@kinow @dbeltrankyl @edgano
The text was updated successfully, but these errors were encountered: