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

Introduce version variable to vscode extension API #2391

Closed
weinand opened this issue Jan 26, 2016 · 4 comments
Closed

Introduce version variable to vscode extension API #2391

weinand opened this issue Jan 26, 2016 · 4 comments
Assignees
Labels
feature-request Request for new features or functionality

Comments

@weinand
Copy link
Contributor

weinand commented Jan 26, 2016

Since we can have different versions of the vscode extension API installed, it would be helpful if there were a way to quickly figure out the installed version.

One way would be to use Intellisense and have a variable "version_0_10_3" that has the version number in its name.

@weinand weinand added the feature-request Request for new features or functionality label Jan 26, 2016
@jrieken
Copy link
Member

jrieken commented Jan 26, 2016

Since we can have different versions of the vscode extension API installed

Unsure if I understand that. it should be defined by the engine version in package.json

@weinand
Copy link
Contributor Author

weinand commented Jan 26, 2016

@jrieken I'm testing #1881 and changing the engine version in package.json does not seem to have any effect. But it's difficult for me figure out what vscode API version is installed because I do not have the API change history in my head. It would be great if intellisense could be used to quickly learn what version of the vscode API is installed.

@jrieken
Copy link
Member

jrieken commented Jan 26, 2016

hm, we do have something like this which I think is the more proper way to go. I understand the intellisense desire but encoding a value as a symbol which changes every release doesn't sound appealing to me

@jrieken
Copy link
Member

jrieken commented Mar 16, 2016

closing by my previous comment

@jrieken jrieken closed this as completed Mar 16, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

2 participants