- Check marketplace enabled state before filtering items
- Check marketplace enabled state before installation
- Use cached state from provider for better performance
- Add console logging for disabled marketplace operations
- Cache marketplaceEnabled state to avoid repeated config lookups
- Update state when experiments change
- Provide cached state through getStateToPostToWebview method
- Check marketplace enabled state before making API calls
- Return empty array when marketplace is disabled
- Add comprehensive tests for network timeout and disabled state
- Consolidate test files into RemoteConfigLoader.spec.ts
- Add 'disableMarketplace' setting to completely disable marketplace functionality
- Add 'marketplaceTimeout' setting to configure API request timeout (1000-60000ms)
- Update RemoteConfigLoader to respect user settings and return empty arrays when disabled
- Update ClineProvider and webviewMessageHandler to check both experiment flag and user setting
- Add better error logging and graceful handling of network timeouts
- Update marketplace button visibility to respect disable setting
- Add comprehensive tests for new functionality
- Update existing tests with proper vscode mocks
This allows users in network-restricted environments to disable marketplace
functionality completely, preventing timeout errors and improving performance.
Add support for the save/discard flow for support prompt setting page
Normally when you edit things on the settings pages, the save button lights up,
allowing you to discard your changes. Currently the prompts page doesn't support this flow-
the prompts are immediately saved when they change.
With this change, we use the normal cachedState system in the SettingView, allowing users to dicard changes to their prompts like any other setting.
This removed the need for the resetSupportPrompt event since we send the entire state of the support prompts (same as before).
Test plan:
* Manually verified prompts can be saved/discarded for different types of support prompts.
* Add reasoning budget support to Bedrock models and update related components
- Introduced `supportsReasoningBudget` property in Bedrock models.
- Enhanced `AwsBedrockHandler` to handle reasoning budget in payloads.
- Updated `ThinkingBudget` component to dynamically set max tokens based on reasoning support.
- Modified `ApiOptions` and `Bedrock` components to conditionally render `ThinkingBudget`.
- Added tests for extended thinking functionality in `bedrock-reasoning.test.ts`.
* Add BedrockThinkingConfig interface and update payload structure
* fix: address PR review feedback (#4481)
- Simplify ThinkingBudget ternary logic since component only renders when reasoning budget supported
- Break down complex thinking enabled condition with clear documentation
- Replace 'as any' usage with proper TypeScript interfaces for AWS SDK events
- Add comprehensive documentation for multiple stream structures explaining AWS SDK compatibility
* feat: show ThinkingBudget component unconditionally
Remove selectedProviderModels.length check to display ThinkingBudget
for all providers, not just those with available models
---------
Co-authored-by: hannesrudolph <hrudolph@gmail.com>
