CommunityToolkit / CommunityToolkit/Tooling-Windows-Submodule
Tooling and app should compile and run when no components are found
- Dominant language
- C#
- Stars
- 55
- Forks
- 19
- Avg merge
- 40m
- Merged PRs (30d)
- 1
Description
## Background
The tooling was created in Toolkit Labs, and was created using CanvasLayout as our testing ground. The tooling has only ever been used with at _least_ one component present.
## Problem
The tooling fails in some places when no components are found. This manifests in various forms.
## Solution
This issue documents and tracks the various problems we've found when no components are present. See comments below.
Contributor guide
Research direction
Start by reproducing the tooling and app with no components present, then review the issue comments for the documented failure points. Done means both the tooling and app compile and run successfully when no components are found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100