fix(widget-builder): Update table sort when field removed or modified #82898
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.
When a field is removed or modified, the sort field should update accordingly. This relies on the fact that we're only going to update one step at a time (i.e. we won't update two fields through the hook in one action) and determines if:
a) a field was removed
b) a field was modified
When a field was removed, we simply reset to the first option.
When a field is modified, we look for which field that was and then update the sort to reflect that field.
I had to fix a bug in the visualize component that was updating the state directly (i.e. directly modifying the memory) instead of updating it through the dispatch method. I fixed this by doing a deep clone and updating the field then calling the dispatch function.