Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quest: add support to popular third-party editor extensions #212

Open
4 of 7 tasks
IgnaceMaes opened this issue Oct 22, 2023 · 4 comments
Open
4 of 7 tasks

Quest: add support to popular third-party editor extensions #212

IgnaceMaes opened this issue Oct 22, 2023 · 4 comments
Labels

Comments

@IgnaceMaes
Copy link
Contributor

IgnaceMaes commented Oct 22, 2023

In order to get top notch editor support like developers expect, third party extensions also need to be taken into account. Because glimmer-js and glimmer-ts are registered as two new language ids with their own respective file extension, most editor extensions will not run on these by default.

Here is a list of popular editor extensions that currently don't work out of the box with .gjs and .gts. This list is by no means exhaustive, so feel free to submit any others.

VS Code

Stand-alone

@SergeAstapov
Copy link
Collaborator

Out of curiosity, is WebStorm considered popular enough editor? or this is more more focused on VS Code?

@IgnaceMaes
Copy link
Contributor Author

According to the 2022 Ember community survey 11% of developers used a JetBrains IDE, compared to 65% using VS Code. It's significantly less, but in an ideal world all major IDEs would be supported.

Realistically, it will come down to someone using a different IDE to submit a list of third-party extensions and work on support, as they have the incentive to do so. If there is such interest, I do think it makes sense to track it here as well.

@SergeAstapov
Copy link
Collaborator

@IgnaceMaes thanks for pointer to survey! That indeed confirms VS Code is the popular one

@IgnaceMaes
Copy link
Contributor Author

Regarding linkedEditing, and related autoClosingTags: these can be accomplished already today by using extensions:

For auto closing of tags, a PR has been opened to enable it by default on glimmer-js and glimmer-ts. (formulahendry/vscode-auto-close-tag#224)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants