Releases: launchdarkly/ld-vscode
Releases · launchdarkly/ld-vscode
[2.2.3] - 2020-03-24
[2.2.2] - 2020-02-24
Changed
- Improved formatting and readability of hover display
- Feature flag metadata used for hover is now cached
[2.2.1] - 2020-02-21
Added
- The hover display surfaces the feature flag's name
[2.2.0] - 2020-01-06
Added
- The extension now contributes a
LaunchDarkly: Configure
command to configure or reconfigure the extension. The extension will prompt users to configure on installation or update, or on obsolete configurations (see Changed section)
Changed
- It is now possible to configure the extension without storing secrets in
settings.json
. Use theLaunchDarkly: Configure
command to configure the extension. With this change, theaccessToken
configuration option is now deprecated, and will be automatically cleared when theLaunchDarkly: Configure
is ran and completed. - The
sdkKey
configuration option is now obsolete. The SDK key will now be inferred from the configured project and environment.
[2.1.2] - 2019-12-26
[2.1.2] - 2019-12-26
Fixed
- Fixed an error log when cursor position was in an invalid state
Changed
- Cleaned up debug logging
- The extension will no longer initially display a warning message when not configured.
2.1.1
2.1.0
[2.1.0] - 2019-06-21
Changed
- Updated dependencies to resolve security vulnerabilities with transitive dependencies.
- Fixed error message typo. Thanks @InTheCloudDan
2.0.4
2.0.3
[2.0.3] - 2018-11-26
Fixed
- The previous version of ld-vscode had shipped with a potentially vulnerable version of
event-stream
, a dependency used by the vscode api. This version downgradesevent-stream
to a previous version that did not contain this vulnerability. More information on this vulnerability can be found here: dominictarr/event-stream#116.