Skip to content

Fix #18431#18445

Merged
nielslyngsoe merged 5 commits intov15/devfrom
v15/bugfix/18431
Feb 25, 2025
Merged

Fix #18431#18445
nielslyngsoe merged 5 commits intov15/devfrom
v15/bugfix/18431

Conversation

@nielslyngsoe
Copy link
Member

Fixes #18431

Does so by making sure the current data respects the order from the persisted data.

This both fixes the case represented in the issue, but also ensures a similar issue that happens with Property Value Presets.
The problem is that we cannot in general be indifferent about array orders in our difference comparison, but in the case of Content Values and Content Variants we can and therefor we can sort them to be like the persisted.
The reason why we go with the persisted, is because persisted is set directly to the version we get back from the server, keeping the order the server insists on. meaning once we got a persisted version we can adjust our to it and avoid differences on values or variant sort orders.

Copy link
Member

@madsrasmussen madsrasmussen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes looks good to me

@nielslyngsoe nielslyngsoe merged commit 33ee144 into v15/dev Feb 25, 2025
23 checks passed
@nielslyngsoe nielslyngsoe deleted the v15/bugfix/18431 branch February 25, 2025 08:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants