microsoft / microsoft/winget-studio

Validate should be an option for a resource in a configuration file

Open
#73 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 Managing a configuration file, the "Validate" is only available on a per-resource level when not in edit mode.
As a user composing my resource, I'd like to validate the resource I'm editing, so that I can see if it gives the result I expect before moving on to the next.

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

Start by tracing the configuration-file resource editing flow and the existing per-resource Validate action. Make Validate available while a resource is being edited, and verify that it reports the resource result before the user moves to the next resource.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.