Move packages to top level under each environment #435
Conversation
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
Co-authored-by: eleanorjboyd <[email protected]>
Co-authored-by: eleanorjboyd <[email protected]>
Copilot
AI
changed the title
[WIP] Move packages to top level under each environment
Move packages to top level under each environment
May 20, 2025
Copilot finished work on behalf of
eleanorjboyd
May 20, 2025 21:27
karthiknadig
requested changes
May 21, 2025
Co-authored-by: karthiknadig <[email protected]>
Copilot finished work on behalf of
karthiknadig
May 21, 2025 17:07
karthiknadig
approved these changes
May 21, 2025
Yoyokrazy
approved these changes
May 22, 2025
NguyenCuong1989
referenced
this pull request
in NguyenCuong1989/vscode-python-environments
Oct 23, 2025
## Problem Currently, in the Python Projects sidebar view, packages are nested under an extra "Packages" dropdown under each environment, creating an unnecessary level of nesting:  ## Changes This PR removes the intermediate "Packages" dropdown and shows packages directly under each environment: - Modified `ProjectView.getChildren()` to skip the PackageRoot level - Updated `ProjectPackage` constructor to accept a `ProjectEnvironment` parent - Updated package refresh logic to work with the new structure - Updated command handlers in `envCommands.ts` to handle the modified package structure - Updated menu condition in `package.json` to attach refresh command to environment nodes After this change, users can access installed packages with just one expansion from the environment level, which improves the user experience by reducing clicks and making the structure more intuitive. Fixes #330. --- 💡 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] <[email protected]> Co-authored-by: eleanorjboyd <[email protected]> Co-authored-by: karthiknadig <[email protected]>
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.
Problem
Currently, in the Python Projects sidebar view, packages are nested under an extra "Packages" dropdown under each environment, creating an unnecessary level of nesting:
Changes
This PR removes the intermediate "Packages" dropdown and shows packages directly under each environment:
ProjectView.getChildren()to skip the PackageRoot levelProjectPackageconstructor to accept aProjectEnvironmentparentenvCommands.tsto handle the modified package structurepackage.jsonto attach refresh command to environment nodesAfter this change, users can access installed packages with just one expansion from the environment level, which improves the user experience by reducing clicks and making the structure more intuitive.
Fixes #330.
💡 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.