microsoft / microsoft/winget-studio

Resource explorer enhancements

Open
#71 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Feature
Dominant language
C#
Stars
67
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Description of the new feature / enhancement

You definitely a local "resource explorer" for the MLP along with the PSModulePath management (to prepend to PSModulePath).
That would also help troubleshooting when a resource is not found.

PSModulePath should be changed only within the WinGet Studio session, but be persistent to WinGet Studio.
Replacing current user's PSModulePath can be a button/option.

Proposed technical implementation details

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names a local resource explorer and PSModulePath session management, but no files, tests, or entry points. Start by locating the existing WinGet Studio UI and PowerShell/module-path handling. Done means the explorer supports troubleshooting missing resources, session changes persist within WinGet Studio, and replacing the current user's PSModulePath is an explicit option.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, powershell
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.