Skip to content

fix(settings): pass through deferLoading and other MCP config fields in mergeMcpServers - #309

Open
raymondginger2018-sudo wants to merge 1 commit into
lessweb:mainfrom
raymondginger2018-sudo:feat/mcp-defer-loading-config
Open

fix(settings): pass through deferLoading and other MCP config fields in mergeMcpServers#309
raymondginger2018-sudo wants to merge 1 commit into
lessweb:mainfrom
raymondginger2018-sudo:feat/mcp-defer-loading-config

Conversation

@raymondginger2018-sudo

Copy link
Copy Markdown

Config-layer half of deferLoading support. mergeMcpServers dropped all fields except command/args/env; now passes through deferLoading, connectTimeoutMs, required, enabledTools, disabledTools, url, headers (project wins / user falls back). Tests: 298 pass / 0 fail. Engine-side support is in #298.

…pServers

mergeMcpServers only kept command/args/env and dropped deferLoading,
connectTimeoutMs, required, enabledTools, disabledTools, url, headers
when merging user + project settings. This made deferLoading:true in
settings.json ineffective at startup.

- Merge all McpServerConfig fields with project-wins/user-fallback
  precedence (same as command/args), booleans use ?? so explicit false
  is preserved
- Add test: resolveSettingsSources preserves deferLoading and extra MCP
  fields (project wins, user falls back)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant