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
Currently we're using a JSON parser to parse the contents of languages.json however this format is pretty unfriendly to contributors, with onerous requirements like no trailing commas (#982).
I'd like to move the parsing to using JSON5 as that is compatible with the current format, so it doesn't require a big change, while also providing a lot QoL improvements like trailing commas and comments.
The text was updated successfully, but these errors were encountered:
Currently we're using a JSON parser to parse the contents of
languages.json
however this format is pretty unfriendly to contributors, with onerous requirements like no trailing commas (#982).I'd like to move the parsing to using JSON5 as that is compatible with the current format, so it doesn't require a big change, while also providing a lot QoL improvements like trailing commas and comments.
The text was updated successfully, but these errors were encountered: