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.
WHY
BEFORE - What was wrong? What was happening before this PR?
It was not possible to register a
retrievedmodel 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
retrievedmodel 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.