You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a section in the docs titled "Core JSON syntax". This sounds really weird to me, as it includes functions, string interpolations and all the other too-wild-to-be-a-JSON perks.
Why is it called "JSON syntax" in the first place? My guess is it's meant to distinguish from string literal syntax, and has nothing to do with JSON. If so, can we call it "object syntax" so people don't expect JSON limitations (like double quotes instead of single quotes and so on)?
The text was updated successfully, but these errors were encountered:
Yep, I am working right now on changing the overall structure and already changed JSON syntax to "Objects based styles syntax". JSON Syntax was used in the older versions before function values.
String interpolations are provided by a plugin though, not in the core, so not sure where you got this.
There is a section in the docs titled "Core JSON syntax". This sounds really weird to me, as it includes functions, string interpolations and all the other too-wild-to-be-a-JSON perks.
Why is it called "JSON syntax" in the first place? My guess is it's meant to distinguish from string literal syntax, and has nothing to do with JSON. If so, can we call it "object syntax" so people don't expect JSON limitations (like double quotes instead of single quotes and so on)?
The text was updated successfully, but these errors were encountered: