Register field events on UpdateOperation edit form #5521
Merged
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.
WHY
BEFORE - What was wrong? What was happening before this PR?
It was not possible to register a
retrieved
model event in fields to run when the entry is retrieved from the database to display on the edit form.Eg:
One would expect that the value of the field would be the json_decoded() version, but this event was never triggered, because the field events were not registered on the update form.
AFTER - What is happening after this PR?
It's now possible to customize model values before the fields attempt to get their respective values by registering a
retrieved
model event on the field.HOW
How did you achieve that, in technical terms?
Called the setup of the model events on the edit form endpoint too.
Is it a breaking change?
It shouldn't, as the retrieved events were not working (and that's the only event that happen when the entry is retrieved from the database), I don't think it's possible to break anything.