71 | | We recommend NAME, because it is shorter and gives more readable json, and gives you flexibility to move around the actual classes if needed without breaking compabibility with existing json files|| |
72 | | |
73 | | |
74 | | Indicates how to include the class name is included in/extracted from the json. |
75 | | |
76 | | ==== |
| 73 | NAME should be used, the others are not properly implemented. We recommend this method anyway, because it is shorter and gives more readable json, and gives you flexibility to move around the actual classes if needed without breaking compabibility with existing json files|| |
| 74 | |
| 75 | The "As" annotation indicates *how* to include the class name is included in/extracted from the json. |
| 76 | |
| 77 | ||As value||meaning|| |
| 78 | ||PROPERTY||The json dict is extended with a {{{type}}} parameter containing the class Id|| |
| 79 | ||WRAPPER_OBJECT||A dict is created with the class Id as key, and as value the actual class contents|| |
| 80 | ||WRAPPER+ARRAY||An array is used for storing the contents of the class|| |
| 81 | |
| 82 | At this moment WRAPPER_OBJECT should be used; the others are not properly implemented. |