Skip to content

Consolidate microsoft-ui-xaml-specs into main repository - #11231

Open
niels9001 wants to merge 5 commits into
mainfrom
consolidate/specs-repositories
Open

Consolidate microsoft-ui-xaml-specs into main repository#11231
niels9001 wants to merge 5 commits into
mainfrom
consolidate/specs-repositories

Conversation

@niels9001

@niels9001 niels9001 commented Jul 10, 2026

Copy link
Copy Markdown
Collaborator

Fixes

N/A - repository documentation consolidation.

PR Type

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Build related changes
  • Documentation content changes
  • Other

Description

Current Behavior

WinUI specifications are split between microsoft-ui-xaml and the separate microsoft-ui-xaml-specs repository.

New Behavior

  • Imports non-duplicate specifications and assets from microsoft-ui-xaml-specs/active.
  • Adds the imported NavigationView specs under specs/NavigationView; Reorganize specs into feature folders #11230 separately moves the existing NavigationView specs into that folder.
  • Uses the active TeachingTip spec and excludes the older duplicate under api_review/teachingtip.
  • Keeps the updated Grid syntax and NavigationView footer specs while excluding their stale duplicate drafts.
  • Moves the WinUI 3 DispatcherQueue spec to specs/DispatcherQueue.
  • Consolidates related specs under clearer folders including Grid, Progress, ProgressBar, ItemsRepeater, ItemsSourceView, and PersonPicture.
  • Moves the archived Tab specification into specs/TabView and removes the obsolete archive structure.

Customer Impact

None. This consolidates specification documents and assets without changing product behavior or APIs.

Regression Potential

  • Low risk - isolated change, limited scope
  • Medium risk - touches shared components or public APIs
  • High risk - architectural or breaking API change

How Has This Been Tested?

  • I have performed a self-review of my own code
  • I have added tests to cover my changes
  • Existing tests pass locally

Imported files were checked for duplicate specifications, content fidelity, destination collisions, and valid relative image links.

Screenshots (if appropriate)

N/A

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 31b7a164-5846-4345-b8d6-372e300a25a8
@microsoft-github-policy-service microsoft-github-policy-service Bot added the needs-triage Issue needs to be triaged by the area owners label Jul 10, 2026
@niels9001
niels9001 marked this pull request as ready for review July 10, 2026 18:56
@niels9001
niels9001 requested a review from a team as a code owner July 10, 2026 18:56
@niels9001
niels9001 requested review from JesseCol and beth-panx July 10, 2026 18:59
niels9001 and others added 4 commits July 10, 2026 21:01
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 31b7a164-5846-4345-b8d6-372e300a25a8
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 31b7a164-5846-4345-b8d6-372e300a25a8
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 31b7a164-5846-4345-b8d6-372e300a25a8
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 31b7a164-5846-4345-b8d6-372e300a25a8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-triage Issue needs to be triaged by the area owners

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant