Skip to content

Conversation

@MartinZikmund
Copy link
Member

GitHub Issue: closes #

PR Type:

What is the current behavior? 🤔

What is the new behavior? 🚀

PR Checklist ✅

Please check if your PR fulfills the following requirements:

Other information ℹ️

Copilot AI review requested due to automatic review settings January 10, 2026 13:31
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR significantly expands and improves the WinUI porting agent instructions, transforming a concise guide into a comprehensive reference document for converting WinUI C++ code to Uno Platform C#.

Changes:

  • Restructured and expanded file layout documentation with detailed examples for each partial file type
  • Added extensive sections on event handling patterns, including inline handlers, CompositeDisposable, and lifecycle patterns
  • Introduced new helper method documentation (GetTemplateChild, SetDefaultStyleKey, ResourceAccessor, SharedHelpers, MUX_ASSERT)
  • Added comprehensive C++ to C# syntax conversion examples
  • Included conditional compilation patterns and TODO comment conventions
  • Added section on porting code snippets with guidance for handling unported dependencies
  • Included WinUI source location reference for easier navigation

@@ -1,312 +1,713 @@
---
name: WinUI Porting Agent
description: Helps with porting of WinUI code from C++ to C#
Copy link

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR description is missing the required issue link. According to repository guidelines, every PR must reference a proper GitHub issue using "Fixes", "Closes", or "Related to" with a fully qualified URL (e.g., Fixes https://github.com/unoplatform/uno/issues/#<ISSUE_NUMBER>). The description currently shows closes # without an issue number.

Copilot generated this review using guidance from organization custom instructions.
Comment on lines +81 to +82
### 2.3. Header File: `ControlName.Header.cs` or `ControlName.h.mux.cs`

Copy link

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent naming convention for header files. The section title (line 81) mentions both ControlName.Header.cs and ControlName.h.mux.cs, but subsequent references use different naming. For example, line 124 refers to .Header.cs while line 677 refers to .h.mux.cs. The document should clarify which naming convention is preferred or if both are acceptable, to avoid confusion for users following the porting guide.

Suggested change
### 2.3. Header File: `ControlName.Header.cs` or `ControlName.h.mux.cs`
### 2.3. Header File: `ControlName.h.mux.cs` (preferred) / `ControlName.Header.cs` (legacy)
- **Preferred for new ports:** `ControlName.h.mux.cs`
- **Legacy/alternate pattern:** `ControlName.Header.cs` (use only when updating existing files that already follow this naming)

Copilot uses AI. Check for mistakes.
@unodevops
Copy link
Contributor

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-22336/docs/index.html

@MartinZikmund MartinZikmund self-assigned this Jan 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants