-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: properly filter palettes #42698
Conversation
Hi @CGNonofr, thanks for the report. What value are you providing to the |
The problem is it is looping of every palettes keys, not only those corresponding to a This is not a problem for other predefined fields because none has a |
I see, @siriwatknp what do you think about this use case? |
I think it's okay to apply this change, the performance should not be different from the existing condition. But I think it should apply to all components. |
@siriwatknp the logic on the filter is getting more complex, should we extract a utility for it so it can be shared throughout the components? Also, should we include this in the v6 milestone? |
Yes, please. I think it's a good addition but not a blocker for beta. |
If there is a palette with a main non-string field, it crashes