CommunityToolkit / CommunityToolkit/Windows
Port BladeView
- Dominant language
- C#
- Stars
- 1.1k
- Forks
- 166
- PR merge metrics
- No merged PRs in 30d
Description
```[tasklist]
### Base Porting Checklist
- [ ] Component name (to `CommunityToolkit.WinUI.Controls.BladeView`)
- [ ] Redesign, following the latest WinUI design guidelines
- [ ] Merge differences from UWP main to WinAppSDK / Uno forks
- [ ] Support for WASM via Uno Platform
- [ ] Improve Samples
- [ ] All brought over tests pass for UWP/WinAppSDK
```
```[tasklist]
### Known Issues
```
```[tasklist]
### Improvements
```
## Notable Changes
N/A
Contributor guide
Research direction
Start by locating the existing BladeView component and its UWP implementation, then compare the WinAppSDK and Uno Platform forks. Review the component, samples, and brought-over tests before tackling the checklist; done means the renamed control, design updates, WASM support, improved samples, and UWP/WinAppSDK tests are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, wasm
- Domain
- design, frontend, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100