Skyhigh173/JSON: fix json_is_valid()

[Procybit]

The function returns false when valid checked JSON is not whitespace-trimmed. Made it check parsed type.

[RockyTheProtogen]

Code no longer returns false when whitespace is introduced.
Fulfils PR but could break existing projects.

[CubesterYT]

I don't think it'll break projects considering projects would've already accounted for this bug and used non whitespace valid json

[RockyTheProtogen]

After a bit of thinking, this shouldn't really affect anything unless projects, for some reason, use a rudimentary way of reading the JSON. Though that is doubted, as the get key block is in this extension.

[GarboMuffin]

this changes the output of

what do you think that should output?

true false 0 "hello" are all valid JSON too, should those not return true here as well?

regardless this will need to be a is_valid_v2 kind of situation since it does affect behavior in ways that we can't really predict

[LSPECTRONIZTAR]

uh this problem is already addressed in #1212

[Procybit]

this changes the output of

what do you think that should output?

true false 0 "hello" are all valid JSON too, should those not return true here as well?

regardless this will need to be a is_valid_v2 kind of situation since it does affect behavior in ways that we can't really predict

Wouldn't additional check for null solve the problem? Previous version worked similar excluding null value, and relied on begin/end characters.

[Skyhigh173]

Just trim trailing and leading white spaces and test it with original script

[Procybit]

So for now it just trims given JSON string before processing it

[GarboMuffin]

okay, i think these blocks need to be replaced but this should be an unambiguous improvement for now