Fix possibly outdated onChange in color palette's color picker #23136
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.
Description
ColorPalette component uses useCallback hook to memoize ColorPicker render function. This memoized renderer is not refreshed when onChange function changes. This causes that onChange function in ColorPicker may become outdated and carries outdated scope. Triggering such an outdated callback may cause issues because it is processed with potentially outdated scope. This PR adds ColorsPalette's onChange callback to the list of dependencies to the memoized ColorPicker render so that the colour picker render method is refreshed after the onChange callback changes.
How has this been tested?
I locally added a component to the ColorsPalette storybook to replicate the issue and checked that the fix works. Without the fix, you can observe that changing colour using the custom colour picker will reset previously set size value.
The component:
Checklist: