Michael

> Thanks, I hadn't heard of that before. I've never used it, either. 😅 I'm just clicking around in our SQL files looking for stuff that seems odd. > I...

T-SQL regressions: ```sql CREATE UNIQUE NONCLUSTERED INDEX IX_some_index ON dbo.some_table( some_column ASC ) ```

What do you think about using `source.json` and `source.json.jsonc`? I worry a little that moving the primary `*.json` association to `source.jsonc` will break a bunch of people and packages' configuration...

Keith, ping me when you're done with this. I'm happy as-is. (Although, granted this is because I'm primarily a T-SQL user. 😉) No pressure for you to add other flavors....

> 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 > ``` >...

Unpivot breaks with no source table alias. This should work: ```sql SELECT item.ID AS DatePivotID, MAX(dDate) AS LastUpdateDate FROM Documents -- add `AS d` to see correct highlight UNPIVOT (dDate...

> It shouldn't even hurt to add the `.basic` and keep it as is. What happens when another syntax `- include: scope:source.json` if you change the root scope to `source.json.basic`?...

> 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. I know...

I think we have a `keyword.operator.bitwise` already.

> I guess all syntaxes should be refactored to use named contexts primarily/only ideally with a common context naming scheme. > > https://github.com/sublimehq/Packages/pull/3659 intents not to mess with current context...