Authoring support for unsealed types
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 665
- Forks
- 134
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
Proposal: Support authoring unsealed types
Rationale
Currently WinRT only allows authoring sealed types. Adding unsealed type support will help adopters such as Windows Community Toolkit, Notifications component, and those who use inheritance. Authors otherwise may use class libraries to work around limitations with sealed classes.
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
The proposal does not identify files, tests, or entry points, so begin by mapping how CsWinRT currently authorizes sealed WinRT types. Define the requirements for authoring unsealed types and verify that inheritance scenarios for the Windows Community Toolkit and Notifications component are supported without the stated class-library workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100