JsonToObject vs Tajson
No edit summary
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
selfVM.JsonToObjects as described here - [[Import xml and JSon with MDriven]] - is available only in ViewModel and will import json from a string and fill in matching attributes and associations from the model starting from an object that JSonToObjects create based on sent in type (first argument).
<message>Write the content here to display this box</message>
<code><span class="col-black">'''selfVM.JsonToObjects'''</span></code> as described here - [[Import xml and JSon with MDriven]] - is available only in ViewModel and will import Json from a string and fill in matching attributes and associations from the model starting from an object that JSonToObjects create based on sent-in type (first argument).  


JSonToObjects offers no transformation layer between your Json and your model - things need to share names to match.
JSonToObjects offer no transformation layer between your Json and your model - things need to share names to match.


The [[Tajson|TaJSon]] strategy is different in that it always uses a ViewModel as a template for both getting and setting data hierarchies to and from json strings. TaJson offers to update object hierarchies in a whole other way than JSonToObjects do as JSonToObjects always creates new objects.
The [[Tajson|TaJSon]] strategy is different in that it always uses a ViewModel as a template for both getting and setting data hierarchies to and from json strings. TaJson offers to update object hierarchies in a whole other way than JSonToObjects do as JSonToObjects always create new objects.  
[[Category:View Model]]
[[Category:View Model]]
{{Edited|July|12|2024}}

Latest revision as of 05:11, 26 June 2024

selfVM.JsonToObjects as described here - Import xml and JSon with MDriven - is available only in ViewModel and will import Json from a string and fill in matching attributes and associations from the model starting from an object that JSonToObjects create based on sent-in type (first argument).

JSonToObjects offer no transformation layer between your Json and your model - things need to share names to match.

The TaJSon strategy is different in that it always uses a ViewModel as a template for both getting and setting data hierarchies to and from json strings. TaJson offers to update object hierarchies in a whole other way than JSonToObjects do as JSonToObjects always create new objects.

This page was edited 3 days ago on 06/26/2024. What links here