Is your feature request related to a problem? Please describe.
Add a helper method to the FeatureFlags class that allows reading feature flag values directly from VS Code settings, enabling users to control experimental features through the standard VS Code settings interface while maintaining the internal Feature Flags system for programmatic control.
Currently, Zowe Explorer uses an internal Feature Flags system (FeatureFlags and FeatureFlagsAccess) for controlling experimental features. However, users cannot easily toggle these features through VS Code's native settings interface. This creates a disconnect between:
- Developer control: Internal feature flags managed programmatically
- User control: VS Code settings that users are familiar with
Describe the solution you'd like
Add a new static method isEnabledInSettings() to the FeatureFlags class that:
- Reads feature flag values directly from VS Code settings
- Does not require ACL permissions
- Provides a simple boolean check with default value support
- Includes built-in error handling
Describe alternatives you've considered
Additional context
Is your feature request related to a problem? Please describe.
Add a helper method to the
FeatureFlagsclass that allows reading feature flag values directly from VS Code settings, enabling users to control experimental features through the standard VS Code settings interface while maintaining the internal Feature Flags system for programmatic control.Currently, Zowe Explorer uses an internal Feature Flags system (
FeatureFlagsandFeatureFlagsAccess) for controlling experimental features. However, users cannot easily toggle these features through VS Code's native settings interface. This creates a disconnect between:Describe the solution you'd like
Add a new static method
isEnabledInSettings()to theFeatureFlagsclass that:Describe alternatives you've considered
Additional context