This repository has been archived by the owner on Jul 29, 2019. It is now read-only.
Releases: XVincentX/vscode-apielements
Releases · XVincentX/vscode-apielements
v0.6.6
v0.6.5
v0.6.5
v0.6.1
v0.6.0
v0.5.0
- It is now possible to configure what you think it's a Symbol to report and not. All of them are extension parameters and are enabled by default.
- The entire codebase has been linted with
tslint
and will continue to be managed in this way - When a
token
is grabbed for the internal Apiary Client, this is now tested on the spot so you do not have to wait until the first usage
v0.4.3
- YAML syntax colorisation has been updated according to the changes made in VSCode repository.
- Drafter.js bundled parser was a beta version by mistake - locked to 2.5.0
- Changelog.md file is now being uploaded to MS Servers. Thanks to my contribution next VSCode version will show the changelog directly from the Extension tab.
v0.4.2
- Provide better error messaging for all failed HTTP requestes.
- The extension is now able to provide the parser output even if there's a parsing error
- Do not throw a error when fetching the same API multiple times as an untitled window
- This extension is not more flagged as preview stuff (finally)
v.0.4.1
v0.4.0
- The Apiary integrated client is now sending the
shouldCommit
parameter (set it totrue
by default). This was driven by offical client update - Browse to API command has been introduced. Just select it on
Apiary
commands and select it. It will try to get the API name from the current file; if it won't be able to understand it, it will show you a dropdown item where you can select the one you want to browse to. - A debounce value for document validation has been introduced, in order to not flood the server process with useless requests whose content is discarded since another one is coming (this is what usually happens when sending keystrokes). The delay value is configurable and it's default value is
1000ms
. Feel free to adjust it with the value that will make you happy. - All the long running operations have now a status bar text so that the user knows something is going on. As next step I would like to add a spinner or an animation.