Lukas W.
Well-known member
Extending the Value Formatter would allow us to define custom types or rules that might be relevant for conversion purposes (as to transition from serialized to json or the other way round smoothly without jobs that potentially take hours to finish and leave data broken until then), as well as to define our own more complex data types. Such changes can agreeably be performed on the entity level for each individual entity, but it feels more natural to attack the problem directly at the root. Any specific reason not to allow this other than "it could mess with your data"?
On my specific task, I'd like to be able to declare a new data type JSON_OR_SERIALIZED, that will always store as json but reads json and serialized alike, so the transition of data is done only when necessary.
On my specific task, I'd like to be able to declare a new data type JSON_OR_SERIALIZED, that will always store as json but reads json and serialized alike, so the transition of data is done only when necessary.
Upvote
2
