Aleksander GrygierandGitHub
38fd5c9993
* fix: drop MCP recommendations auto-popup and silent preloads * feat: Add consent-driven MCP recommendations inside Add New Server dialog * refactor: Drop mcpDefaultServerOverrides for mcpServers[i].enabled * feat: Center the empty state on the MCP settings page * fix: keep existing MCP cards intact when adding a new server * fix: keep MCP cards stable when a new server is added * refactor: keep MCP server list in config insertion order * feat: shrink the recommended-MCP cards to two tools each and fit them in one row * feat: make recommended MCP cards click-to-fill and tighten copy * feat: highlight the selected MCP recommendation and stop auto-focus on dialog open * feat: derive MCP recommendation selection from the form URL * fix: make recommendation MCP cards fully non-focusable * fix: redirect focus from first card to the URL input on consent * chore: Formatting * refactor: Remove Recommended MCP Servers completely * fix: Preserve legacy mcpDefaultServerOverrides key after merge migration for downgrade compatibility
20 lines
838 B
TypeScript
20 lines
838 B
TypeScript
import { describe, expect, it } from 'vitest';
|
|
import { SETTINGS_KEYS } from '$lib/constants/settings-keys';
|
|
|
|
/**
|
|
* Default-value policy for the `MCP_SERVERS` setting.
|
|
*
|
|
* Earlier versions of the UI preloaded a hard-coded list of suggested
|
|
* MCP servers into this setting on first install. That caused silent
|
|
* third-party HTTP requests at app load (see issue #25509) and a popup
|
|
* "recommendation" dialog (see issue #25274). New users must now opt
|
|
* in explicitly when adding a server, so the default is an empty list.
|
|
*/
|
|
describe('MCP_SERVERS default value', () => {
|
|
it('does not preload any servers in the MCP_SERVERS setting default', async () => {
|
|
const { SETTING_CONFIG_DEFAULT } = await import('$lib/constants/settings-registry');
|
|
|
|
expect(SETTING_CONFIG_DEFAULT[SETTINGS_KEYS.MCP_SERVERS]).toBe('[]');
|
|
}, 15000);
|
|
});
|