Skip to content

Conversation

evoactivity
Copy link
Member

VSCode determines the language to filter snippets by from the caret position in a file. Inside a GTS or GJS file the outer scope is "typescript" and "javascript" respectively.

Originally tried changing this so the outer scope language was glimmer-ts or glimmer-js but this caused the js/ts language features to never activate for a gts/gjs file.

@NullVoxPopuli
Copy link
Member

I wonder if we should publish two packages?

one for vscode, one for not-vscode?

that way there are no compromises. hmm

@evoactivity
Copy link
Member Author

Probably best option for forseeable future.

We can generate a different package.json with some argument to the generate script.

I'm not familiar with publishing for neovim, is that something we can automate?

@NullVoxPopuli
Copy link
Member

I'm not familiar with publishing for neovim, is that something we can automate?

neovim uses git references directly, so we'd probably make a separate branch and tags for neovim publishes, and then instructions would be like:

use { 'ember-tooling/snippets', branch = 'neovim-1.x' }
-- or
use { 'emebr-tooling/snippets', tag = '[email protected]' }

or something like that

@NullVoxPopuli NullVoxPopuli changed the base branch from main to vscode/main August 28, 2025 02:47
@NullVoxPopuli NullVoxPopuli added the enhancement New feature or request label Aug 28, 2025
@NullVoxPopuli NullVoxPopuli merged commit 7e4eb37 into vscode/main Aug 28, 2025
2 checks passed
@NullVoxPopuli NullVoxPopuli deleted the widen-language-scope branch August 28, 2025 02:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants