You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we are dealing with proper code tree transformations, it might be considerable to incorporate odoo-pylint conformance scripts in order to facilitate to move legacy code base towards an OCA compliant state.
As we have pre-commit checks in place, since v13.0.
The text was updated successfully, but these errors were encountered:
I'm in favour to remove black call and call pre-commit run -a if pre-commit is installed and pre-commit git file is present.
So, the lib will be adapted to the quality policy of the current repo. @lmignon : what do you think ?
I would personally not include a pre-commit nor black nor anything of this kind in this tool. This adds complexity and maintenance burden while imposing a specific workflow to users, and pre-commit can be combined as user wish with a couple line script or any other approach.
As we are dealing with proper code tree transformations, it might be considerable to incorporate
odoo-pylint
conformance scripts in order to facilitate to move legacy code base towards an OCA compliant state.As we have pre-commit checks in place, since v13.0.
The text was updated successfully, but these errors were encountered: