Johannes Rappen
Johannes Rappen
Will do when I'm back home.
I did some "comment"s research. The built-in converter had originally brought over the comment tags from tmLanguage, when I did a PR to convert all files to sublime-syntax. I haven't...
v2 syntaxes should use `pop: 1` instead of `pop: true`
⚠️ This is a first step to show my current work in progress. There is still a lot of work to do. Please comment below with suggestions.
* Could you check if this fixes #1742 and #1764 and add that to the opening comment (i.e. the commit message)? * Were you going to add PostgreSQL as well...
As @jskinner requested in #285, this PR applies `JSONC` to `*.json` files by default to not confuse beginners too much who do not know how to set a syntax for...
Sounds reasonable. I haven't looked at other packages that either use JSON or are affected by this change, yet.
```text . └─ SQL ├─ tests │ ├─ indentation # rules defined but not backed up by tests, yet │ ├─ symbols # any plans? explained in sublimehq/sublime_text#3154 for ST4087+...
Ok, follow up question, should I change stuff like: ```yaml scope: comment.line.double-slash.jsonc ``` to ```yaml scope: comment.line.double-slash.json.jsonc ``` for `JSONC.sublime-syntax`?
@keith-hall I sent you forkeith/Packages#10 for some suggested edits