Only reset unsaved changes when value has changed #190103
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates
resetUnsavedChanges
to only callsetter
when the resetting changes the value. The reason for this is that with the old logic, all keys would get set, triggering all sorts of subscriptions. For example, data controls fetch new data views when dataViewId changes. This action should only be triggered when dataViewId actually changes on reset and not on a reset where dataViewId is not changed