-
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
[IMP] pre-commmit: Run prettier and eslint as local hooks and update versions in v18 #278
Conversation
3635480
to
d12dbc6
Compare
@sbidoul I made the Also, pre-commit was failing, due to the |
d12dbc6
to
046aab0
Compare
Is it not necessary to convert eslintrc.yml to cjs, and to the new eslint 9 config format for v18? We could also upgrade node for v18. BTW, I wonder why GitHub is still trying to run the tests for 11 and 12. |
Will do that, I thought it was something limited to prettier, but it does appear to have changed as well. Guess that's the new way of doing configuration files in the javascript world.
I will look into it, see what version makes most sense.
Yeah that's weird, maybe something's still cached on GitHub's side? |
779ac1d
to
5562915
Compare
I've migrated the eslint configuration to the new format following both eslint and jsdoc guides. Most parts have been migrated using the configuration migrator, but some, such as jsdoc settings, were done by hand. I also set I also update the node to version 22, which is the latest TLS release, and fixed some issues with prettier. |
Hi @PabloEForgeFlow I did a test by applying the template from your PR onto OCA/storage#399 I noticed two things:
|
…clude new .cjs ones
5562915
to
8691113
Compare
Makes sense, I added a line to |
@@ -5,6 +5,7 @@ _min_copier_version: "9" | |||
|
|||
_tasks: | |||
- rm -f {% if ci != "Travis" %}.travis.yml{% endif %} .t2d.yml | |||
- rm -f .prettierrc.yml .eslintrc.yml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@PabloEForgeFlow these should be removed only for odoo_version >= 18, right? Can you adjust that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in 6f0c788
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I though they would be recreated, but yeah it's probably more clear this way.
Should fix #264 and #224.