[FLOW3-general] JSON transformation

[Adrian Föder]

Hi Sebastian,

thanks at all for caring about my idea; so because it's a good decision 
to set that to the property mapper I'll stop that discussion here in the 
List and move to the issue you already mentioned: 
http://forge.typo3.org/issues/32106

 > PS: I'm on holidays next week ;)

"holidays"? Is that a new FLOW3 convention I've not yet heard of? ;-)


Thanks and best!
-adrian

On 09.03.2012 07:15, Sebastian Kurfürst wrote:
> Hey Adrian,
>
>>> See http://forge.typo3.org/issues/32106 for an indepth concept by me.
>>
>> I feared you would refer to that issue entry I already tried to
>> understand ;-)
> If you have questions to it let me know, then we can discuss it!
>
>> In my own sandbox, the idea of having a central configuration that
>> defines the json-representation of each entity gets more and more
>> fancy to me. But maybe all of you say that wasn't a good idea.
> What I could imagine is the following:
>
>    * Extend Property Mapping to support the reverse direction "object ->
>      Simple Type", and also under a specific "context".
>    * For JSON, you'd then call property mapping "object ->  array" under
>      the context "json"
>    * the resulting array would then be json_encoded.
>
>
> The type converter configuration from object to JSON could then be
> defined globally via settings.yaml or overridden using type converter
> specific configuration.
>
> What do you think?
>
> Greets,
> Sebastian
>
> PS: I'm on holidays next week ;)