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
Is your feature request related to a problem?
Yes, the issue arises with the migration to Odoo 18, where the use of the
tag has been replaced with the tag to handle the Chatter component in views. The current pre-commit hook does not detect the deprecated usage of
in XML files, which could lead to compatibility issues with Odoo 18.
Reference: odoo/odoo#156463 explains this change in detail.
Describe the solution you'd like
I propose enhancing the pre-commit hook to detect and raise a warning or error when
is used instead of . This will help developers identify and fix deprecated code patterns before committing, ensuring compatibility with Odoo 18.
Specifically, the hook should:
Identify instances of
in XML files.
Provide a clear message suggesting the use of instead.
Optionally, provide a quick fix or automated replacement for the deprecated tag.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Yes, the issue arises with the migration to Odoo 18, where the use of the
tag has been replaced with the tag to handle the Chatter component in views. The current pre-commit hook does not detect the deprecated usage of
in XML files, which could lead to compatibility issues with Odoo 18.
Reference: odoo/odoo#156463 explains this change in detail.
Describe the solution you'd like
I propose enhancing the pre-commit hook to detect and raise a warning or error when
is used instead of . This will help developers identify and fix deprecated code patterns before committing, ensuring compatibility with Odoo 18.
Specifically, the hook should:
Identify instances of
in XML files.
Provide a clear message suggesting the use of instead.
Optionally, provide a quick fix or automated replacement for the deprecated tag.
The text was updated successfully, but these errors were encountered: