Release PR for 2.2.0. Contains some additional cleanup and fixes.
Although there is a potential breaking change in this release (see last bullet point in change notes), it's more-so of a bug fix considering the possibility of mismatched sdk / env keys being configured was not intended.
[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 the LaunchDarkly: Configure command to configure the extension. With this change, the accessToken configuration option is now deprecated, and will be automatically cleared when the LaunchDarkly: 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.
Release PR for 2.2.0. Contains some additional cleanup and fixes.
Although there is a potential breaking change in this release (see last bullet point in change notes), it's more-so of a bug fix considering the possibility of mismatched sdk / env keys being configured was not intended.
[2.2.0] - 2020-01-06
Added
LaunchDarkly: Configurecommand 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
settings.json. Use theLaunchDarkly: Configurecommand to configure the extension. With this change, theaccessTokenconfiguration option is now deprecated, and will be automatically cleared when theLaunchDarkly: Configureis ran and completed.sdkKeyconfiguration option is now obsolete. The SDK key will now be inferred from the configured project and environment.