Sunday, September 18, 2022
2 changes · master
Resolved issues and error corrections
Form labels are now matched to fields using only visible view identifiers instead of internal technical IDs. This prevents labels from appearing blank or attaching to the wrong field, especially when forms contain repeated field names.
Original PR description
with its label Before this commit, when compiling the field to link the field with a previously found label, to search, we used in order : the 'id' (encoded on the arch), the 'field_id' (an internal technical ID), the 'name' (also in the arch). The issue with this is that the "field_id" is a technical id and shouldn't be used, to search the label. Now, we only search for the 'id' and the 'name'.
Records now keep the information needed by views while they are loading, instead of being temporarily emptied. This prevents kanban views from crashing during refreshes and makes record loading more reliable for users.
Original PR description
Before this PR, when a record from a relational model would start to load, it would empty its `data` object. The issue is that a rendering process can be initiated right after a record started loading. In kanban views, this causes a crash since all records are always assumed to contain values in their data objects. This PR takes care to only clean strictly unwanted data when loading a record instead of removing all the values, ensuring that records always contain data. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr