JsonToObject vs Tajson
No edit summary |
(Automatically adding template at the end of the page.) |
||
| (2 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). | <code>selfVM.JsonToObjects</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 | 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 | 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 15:36, 10 February 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 more than 11 months ago on 02/10/2024. What links here