microsoft / microsoft/winget-studio

Changes made but not "updated" warning

Open
#141 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

When I'm editing a configuration file, I might make a change to the settings and navigate away before hitting "update". It would be nice if I got some kind of a warning when that happens.

If I edit settings for one resource settings and go to modify another one, my changes are lost when I come back.

Maybe there should be an indication that changes are pending in the UI view (as opposed to the code view) that I have pending "unsaved [Updated]" changes.

I'd also like to be able to "clear" my pending changes if I change my mind.

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

No files, tests, or entry points are named. Start by locating the configuration-editing UI and the navigation path between resources. Done means unsaved changes are clearly indicated, navigating away warns before they are lost, and users can clear pending changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.