Skip to content

Conversation

@iccir
Copy link
Contributor

@iccir iccir commented Dec 25, 2025

This implements #4419 and updates all test cases. For consistency, I also changed the is operator in TypeScript to be keyword.operator.word.is.js (I can back this out if needed). All keyword.operator.word.js scopes should now be specific.

Closes #4419

keith-hall
keith-hall previously approved these changes Dec 25, 2025
jrappen
jrappen previously approved these changes Dec 25, 2025
@jrappen jrappen changed the title Use more-specific scopes for in/of/is (#4419) [JavaScript] Use more-specific scopes for in/of/is Dec 25, 2025
Copy link
Collaborator

@deathaxe deathaxe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We probably want to use the chance to align JavaScript scopes to existing best practices.

Related with PRs #4227 and #4271.

@iccir iccir dismissed stale reviews from jrappen and keith-hall via bfef8da December 25, 2025 15:43
@deathaxe deathaxe merged commit c4425f3 into sublimehq:master Dec 27, 2025
2 checks passed
deathaxe added a commit to deathaxe/sublime-packages that referenced this pull request Dec 27, 2025
This commit scopes logical `in` keyword `keyword.operator.logical`,
following the scheme of PR sublimehq#4227 and sublimehq#4271 as a follow-up of sublimehq#4420.

It fixes a syntax test, using invalid syntax `for (var in list)`,
in which `in` was scoped logical keyword due to `var` not being a
valid iterator variable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[JavaScript] Use more-specific scopes for in/of

4 participants