Fix filter to use translated labels for enums implementing TranslatableInterface#7576
Merged
javiereguiluz merged 1 commit intoMay 1, 2026
Conversation
Contributor
|
Maybe related to #7243 |
javiereguiluz
force-pushed
the
fix/filter-translatable-backed-enum
branch
from
72c05ad to
e4890bb
Compare
Collaborator
|
Thank you Louis-Arnaud! Merged in 4.x and 5.x. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 backed enum implements
TranslatableInterfaceand is passed toChoiceFilter::setTranslatableChoices(MyEnum::cases()), the filter submitted the list indices (0, 1, 2, ...) instead of the enum values, so no row ever matched.The fix detects a list of
UnitEnum/BackedEnumcases and uses their backing values (or names) as submitted values, keeping the enum instances as labels soTranslatableInterfacekeeps working.Fixes #7571