All notable changes to the "launchdarkly" extension will be documented in this file.
- Numerous performance issues related to code lens.
- Initial setup now recovers better if there's been a problem.
- Initial setup is now split into Sign in and Configuration.
- Updated CLI version of Code References.
- Code lens and hover now show SDK availability of a flag.
- Sign via through AuthProvider API.
LaunchDarkly: Flag Actions
command.- Quick Targeting allows you to add/remove single context or rule from a flag.
- Flags in File now has inline commands on entry.
- Status bar icon that tells you current configured project and environment.
- Fixed error switching instance urls
- Fixed alias support on hover
- Fixed handling of project and environment configuration
- Added additional guards on validation of API calls
- Fixed readiness check
- Fixed error with automatic migration of API tokens
- Moved Flag tree view to new LaunchDarkly Explorer view
- API Tokens are now stored using Secrets API
- Quick Links to various LaunchDarkly pages
- Create flags from VS Code
- Find flags in file view
- New command
LaunchDarkly: Toggle Flag
to toggle flags from command palette
- Various fixes for streaming connections
- Updates for Marketplace
- Update icon
- Show flag status(on/off) at top level of treeview
- Only update flags on refresh schedule for global metadata
- Added "Feature Flag Explorer" to Explorer Container. Provides a list view of all feature flags and their targeting in current environment.
- Added "Open in browser" link to hover display
- Improved formatting and readability of hover display
- Feature flag metadata used for hover is now cached
- The hover display surfaces the feature flag's name
- 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)
- 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.
- Fixed an error log when cursor position was in an invalid state
- Cleaned up debug logging
- The extension will no longer initially display a warning message when not configured.
- The extension is now bundled with webpack to reduce artifact size (5.8mb -> 800kb)
- Updated dependencies to resolve security vulnerabilities with transitive dependencies.
- Fixed error message typo. Thanks @InTheCloudDan
- Locked indirect dependency
node.extend
to versions ^1.1.7.
- 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.
- Fixed a bug causing hovers on non-flag string literals to indefinitely display loading text
- Configuration settings no longer require manually editing the json settings file
- The extension no longer requires a restart to apply configuration changes
- The LaunchDarkly base and stream uris are now configurable
- Added configuration options to disable flag key autocomplete and hover
- A new "Open in LaunchDarkly" command which opens the feature flag key at the current editor position in the LaunchDarkly dashboard.
- Removed the "Get feature flag" command
- Flag keys with non-letter characters are now correctly discovered by the extension
- Flag autocomplete suggestions will now only be generated when inside of a string literal
- Server connections generated by the extension will now correctly be identified as generated by the extension
- Initial release