Refresh environment managers automatically when expanding tree node#783
Merged
eleanorjboyd merged 5 commits intomainfrom Sep 8, 2025
Merged
Refresh environment managers automatically when expanding tree node#783eleanorjboyd merged 5 commits intomainfrom
eleanorjboyd merged 5 commits intomainfrom
Conversation
Co-authored-by: eleanorjboyd <26030610+eleanorjboyd@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Expanding
Refresh Pipenv environments automatically when expanding tree node
Sep 3, 2025
Pipenv should refresh the children
Member
|
do this for any manager not just pipenv @copilot |
Co-authored-by: eleanorjboyd <26030610+eleanorjboyd@users.noreply.github.com>
Contributor
Author
Done! I've updated the implementation to refresh all environment managers when expanded, not just Pipenv. The change removes the |
Copilot
AI
changed the title
Refresh Pipenv environments automatically when expanding tree node
Refresh environment managers automatically when expanding tree node
Sep 5, 2025
eleanorjboyd
approved these changes
Sep 8, 2025
Tyriar
approved these changes
Sep 8, 2025
NguyenCuong1989
referenced
this pull request
in NguyenCuong1989/vscode-python-environments
Oct 23, 2025
…#783) When expanding environment manager nodes in the Environment Managers view, newly created environments (such as those created by `pipenv install pytest` or `conda create -n myenv`) were not appearing until the user manually refreshed the view. This change adds automatic refresh functionality for all environment managers when their tree node is expanded. The implementation: - Calls the existing `manager.refresh(undefined)` method before retrieving environments for any manager type - Affects all environment managers (Pipenv, Conda, Venv, Poetry, etc.) providing consistent behavior - Uses the established refresh mechanism that properly updates collections and fires change events **Before:** 1. Run `pipenv install pytest` or create a new environment with any manager 2. Open Environment Managers view 3. Expand environment manager node 4. New environment is not visible until manual refresh **After:** 1. Run `pipenv install pytest` or create a new environment with any manager 2. Open Environment Managers view 3. Expand environment manager node 4. New environment appears immediately The fix is minimal and targeted, modifying only 1 line of code in the `getChildren` method in `EnvManagerView`. Unit tests have been updated to validate the core logic for any manager type. Fixes #782. <!-- START COPILOT CODING AGENT TIPS --> --- 💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more [Copilot coding agent tips](https://gh.io/copilot-coding-agent-tips) in the docs. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: eleanorjboyd <26030610+eleanorjboyd@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When expanding environment manager nodes in the Environment Managers view, newly created environments (such as those created by
pipenv install pytestorconda create -n myenv) were not appearing until the user manually refreshed the view.This change adds automatic refresh functionality for all environment managers when their tree node is expanded. The implementation:
manager.refresh(undefined)method before retrieving environments for any manager typeBefore:
pipenv install pytestor create a new environment with any managerAfter:
pipenv install pytestor create a new environment with any managerThe fix is minimal and targeted, modifying only 1 line of code in the
getChildrenmethod inEnvManagerView. Unit tests have been updated to validate the core logic for any manager type.Fixes #782.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.