You are not logged in.
Pages: 1
This is no valid JSON.
Even this RFC defines an object as member = string name-separator value
So the field name should be a string. And the RFC states that " A string begins and ends with quotation marks. "
For instance, no browser would be able to parse it.
See https://www.json.org/json-en.html
The mORMot parser can understand some "extended" JSON, as used in MongoDB, with unquoted alphanumerical field names, but not being numbers.
Even from JavaScript, {field:"none",1:"down",2:"up"} is accepted, but {field:"none",-1:"down",2:"up"} is not. And this is JavaScript, not JSON.
Online
Pages: 1