Startseite Erkunden Hilfe
Anmelden
TorqueEngine
/
Torque2D
Mirror von https://github.com/TorqueGameEngines/Torque2D.git
2
0
Fork 0
Dateien Issues 0 Wiki
Struktur: c2b65c9fd1
Branches Tags
Torque2D
/
engine
/
source
/
persistence
/
rapidjson
/
bin
/
jsonchecker
MelvMay-GG 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
..
fail1.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail10.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail11.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail12.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail13.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail14.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail15.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail16.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail17.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail18.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail19.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail2.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail20.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail21.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail22.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail23.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail24.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail25.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail26.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail27.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail28.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail29.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail3.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail30.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail31.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail32.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail33.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail4.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail5.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail6.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail7.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail8.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
fail9.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
pass1.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
pass2.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
pass3.json 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren
readme.txt 1d007c26a4 - TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false). vor 12 Jahren

readme.txt

Test suite from http://json.org/JSON_checker/.

If the JSON_checker is working correctly, it must accept all of the pass*.json files and reject all of the fail*.json files.