JSON primitives support

[un000]

How can I highlight json like
123
Or
"random string"
because these are valid JSONs.

Thank you!

[mac-s-g]

@un000 what behavior would you like to see with valid JSON input that is not an array or an object?

[un000]

I have JSON-schema like this:

It means that JSON

123

is being interpret as valid.
123 will be a root element and equals 123

The same is for boolean, float, string and null.

[un000]

I did some changes here #125 to show what I want.

But for now it's hard to implement the copy & edit button

[ajbdev]

Not to nitpick, but a primitive is not valid JSON according to the JSON spec. I only know this because of time I've spent banging my head against the wall a lot when using a fairly strict parser against an API that was rather flexible with it's return values.

Here's a good SO answer on the topic: https://stackoverflow.com/questions/41732737/is-a-primitive-type-considered-json

Perhaps given the goals of the project it might be better just to render the primitive, but it might catch some people by surprise if this doesn't error out as invalid.

[un000]

https://tools.ietf.org/rfc/rfc7159.txt
Just look the rfc

“Hello world” is the valid string

Also, all parsers supports this feature, they are PHP(json_decode), Js(JSON.Parse), PostgreSQL (json/jsonb-type)

[ajbdev]

I retract my comment then. Looks like the RFC I was referencing is outdated. Good to know!

[awesomesk1ll]

sup: do it please

I was disorientated by the validation error, and so I came here.
It's bad if the user has to come here because they see unexpected behavior.