-
Notifications
You must be signed in to change notification settings - Fork 16
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
Renaming #366
Comments
Renaming brings less clarity for developers who already use UELS, thing may help here, is transform https://github.com/ember-tooling/vscode-ember to extension pack and mention See extension pack documentation: https://code.visualstudio.com/blogs/2017/03/07/extension-pack-roundup It allow developers to install "official extension" and get uELS as it's dependency |
Came here to say this. It honestly couldn't be more confusing, especially when it's presently very difficult to find which plugins/addons/etc are "stable" and future-ready in the Ember ecosystem. |
Agree, please consider a rename. I constantly have to tell new engineers that this "Unstable" addon is actually the stable one 😅 |
Let it be |
I'm not closing issue, because may be a case if I need to update vscode namespace and unpublish existing extension. (in a month or such) |
Hi @lifeart.
What do you think about renaming the 'Unstable Ember Language Server' to less confusing?
UELS
is the main VSCode extension for Ember environment. The nameUnstable Ember Language Server
may to confuse new Ember developers. After the renaming we can to remove the explanations forUnstable
in the name.It may be
Power Ember Language Server
orEpic Ember Language Server
or other what you like.The text was updated successfully, but these errors were encountered: