- Issue created by @just_like_good_vibes
- Merge request !266Issue #3488044 by just_like_good_vibes: Fix 'submitted value is not allowed' in component prop form → (Merged) created by just_like_good_vibes
- 🇫🇷France just_like_good_vibes PARIS
That was quite hard to do in fact, harder than i thought because of the way and order in which the form is processed.
The bug really only occurs in prop forms, when a switch source is triggered from the select source.
the input of the old source is getting submitted through the ajax handler and it is difficult to clean the data, early at the appropriate moment, before the bug is thrown (invalid value for the select). unfortunately, it seems not really doable in the prop form, which would have been a good place. Like when we switch source for prop, we then clean the "source" settings.so i propose for now this implementation, only in the derivableContext source.
As soon as the invalid value is detected, it is cleaned and then we had to cover the ongoing form validation process.
The value needed to be clean, but not in form state values unfortunately but rather in form state input (because they are latter processed to overwrite the form state values). - First commit to issue fork.
-
pdureau →
committed e6a1e80d on 2.0.x authored by
just_like_good_vibes →
Issue #3488044 by just_like_good_vibes: Fix 'submitted value is not...
-
pdureau →
committed e6a1e80d on 2.0.x authored by
just_like_good_vibes →
Automatically closed - issue fixed for 2 weeks with no activity.