JsonToObject vs Tajson
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
selfVM.JsonToObjects as described here [[Import xml and JSon with MDriven]] is available only in | 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 offers no transformation layer between your Json and your model - things need to share names | JSonToObjects offers 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 | 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. | ||
[[Category:View Model]] | [[Category:View Model]] | ||
Revision as of 06:17, 22 February 2023
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 offers 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 creates new objects.
This page was edited 99 days ago on 02/10/2024. What links here