Johannes Rappen
Johannes Rappen
> JSON with Comments (jsonc) is just an extension of JSON. I don't therefore see any value in adding a _JSON (Basic)_ which _JSON_ is derived from by just adding...
@keith-hall this PR also: * fixes #3072 * closes #2631 --- Maybe you could add that to the opening comment (i.e. the commit message for the PR)?
Probably not. Unless I have to extract bits from `JSON (Basic)` to `JSON`. It's easier to merge than separate them later.
> If so, what? In that case I'd assume nothing.
Could use this instead, though: ```yaml - include: scope:Packages/JSON/JSON.sublime-syntax ``` unless I'm mistaken. I have a vague memory seeing this somewhere.
Sometimes, breaking stuff is the way forward. No need for that here, though.
On the other hand, the **package you linked** from across the internet I will definitely break, cause he'd have to switch to `scope:source.json.jsonc#prototype` as `JSON` won't have that (i.e. comments)...
Does anybody know of any JSON flavors that do accept decimal floats with leading or trailing periods in the base? In basic JSON they apparently are illegal (and weren't scoped...
⚠️ I have addressed and resolved all comments above, except for the one about `meta_include_prototype`. --- Decimal floats are now forced to a more explicit format.
Thoughts on `embed: scope:source.json` in: - LaTeX - Markdown - Perl - PHP Source and `push: scope:source.json` in: - PHP Source anyone?