microsoft / microsoft/WinAppVSCE
Enhancement: Enforce maxOccurs and xs:choice exclusivity in schema validation
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 3
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 11
Description
Deferred from PR review follow-up. Current schema validation does not yet enforce maxOccurs limits or xs:choice exclusivity. Track implementing both behaviors in manifest schema validation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the manifest schema validation entry point and review the deferred PR follow-up context. Implement enforcement for maxOccurs limits and xs:choice exclusivity, then verify that manifest validation rejects schemas violating either rule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100