Skip to content

Fix environment extension activation with scoped settings - #26117

Open
Eleanor Boyd (eleanorjboyd) wants to merge 1 commit into
microsoft:mainfrom
eleanorjboyd:fix-environments-extension-scope-activation
Open

Fix environment extension activation with scoped settings#26117
Eleanor Boyd (eleanorjboyd) wants to merge 1 commit into
microsoft:mainfrom
eleanorjboyd:fix-environments-extension-scope-activation

Conversation

@eleanorjboyd

Copy link
Copy Markdown
Member

Summary

  • align useEnvExtension() with the Python Environments extension's window-wide explicit-disable rules
  • fall back to the legacy environment path when any configuration scope explicitly disables Python Environments
  • add regression coverage for conflicting global/workspace values and the enabled path
  • isolate the memoized activation decision between tests

Fixes #26068

Validation

  • ./node_modules/.bin/tsc -p ./
  • ESLint on the changed source and test files
  • focused affected suites: 32 passing, 3 pending
  • full unit suite: 5,170 passing, 36 pending, with 2 unrelated existing Posix Known Path Locator failures

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

Python activation fails when environment extension settings conflict across scopes

2 participants