@kenneth-vkd We're currently discussing whether this should be a valid use-case or not before applying my patch at #43354
Can you explain why do you need the key to be case-sensitive? Is it just because of migration ease from 12.0 to 13.0? The key for selection fields are for internal reference only, the only thing that should be important is the label.
It was not an intended change from 12.0 to 13.0 but it was the product of a heavy refactoring of Selection fields since they had many other, more impactful problems but I fail to see why it would be a problem other than conveniency.
The problem is not whether we can "fix" the behaviour to be like 12.0 or not, but whether it is worth the effort is complexifying migrations from 13.0 to 14.0, so we're debating whether this should be a legit use-case or throw a warning if it happens
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.