fix: force model's item bindings to re-render in template renderer

[vursen]

Description

When calling setProperties(...) to re-render a Polymer template instance, it compares the new properties with old ones using the === operator to skip rendering not changed properties.

However, in case of an object property, the === operator can't determine whether the object has been mutated inside. Thus, the property won't be re-rendered when mutated.

This issue appears in the template renderer when mutating the model.item object after it is bound to a template.

This PR introduces a workaround that forces model.item template bindings to re-render even the new item is strictly equal to the old item.

Type of change

• Bugfix

Checklist

• I have read the contribution guide: https://vaadin.com/docs-beta/latest/guide/contributing/overview/
• I have added a description following the guideline.
• The issue is created in the corresponding repository and I have referenced it.
• I have added tests to ensure my change is effective and works as intended.
• New and existing tests are passing locally with my change.
• I have performed self-review and corrected misspellings.

Additional for Feature type of change

• Enhancement / new feature was discussed in a corresponding GitHub issue and Acceptance Criteria were created.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication