microsoft / microsoft/WinAppVSCE
IntelliSense: auto-insert xmlns declarations for undeclared namespace completions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 3
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 11
Description
Summary
IntelliSense intentionally hides namespaced elements/attributes until the user has already authored the matching xmlns: declaration, blocking discovery of manifest features.
Details
- Child completion drops any schema child whose namespace is not already declared in the manifest
- Users can't discover
uap:,desktop:,com:features from a minimal manifest - This is by design currently (tested behavior) but limits discoverability
Recommendation
Offer completions using canonical schema prefixes even when the namespace is missing, and attach additionalTextEdits to add the root xmlns: declaration automatically.
Surfaced by PR review skill (alternative-solution dimension)
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 IntelliSense child-completion logic that filters undeclared namespaces and review the existing tests for this behavior. The work is done when namespaced elements and attributes are offered with canonical prefixes and the root xmlns declaration is added through additionalTextEdits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100