Tooling-Windows-Submodule icon indicating copy to clipboard operation
Tooling-Windows-Submodule copied to clipboard

Community Toolkit infrastructure for use as a submodule 'tooling' directory in other repositories.

Results 88 Tooling-Windows-Submodule issues
Sort by recently updated
recently updated
newest added

# Background Labs targets both WinUI 2 and WinUI 3. Since this means 2 different namespaces _everywhere_ for fairly common things, we have several "GlobalUsing" .cs files in the [common](https://github.com/CommunityToolkit/Labs-Windows/tree/main/common)...

enhancement
dev loop ➰

### Describe the bug These are in two different namespaces `Windows.System` for UWP and Microsoft.UI.Dispatching` for WinAppSDK. We currently don't include these in our global using in https://github.com/CommunityToolkit/Labs-Windows/blob/main/common/GlobalUsings_WinUI.cs This means...

bug :bug:
enhancement
dev loop ➰
templating

### Describe the bug Many samples need the option to perform an action or demonstrate a triggered event (like a notification for instance). For instance, the current notification behavior needs...

enhancement

## 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...

bug :bug:
enhancement
dev loop ➰

## Background In https://github.com/CommunityToolkit/Labs-Windows/pull/75, we added a [`UseUnoWinUI.ps1`](https://github.com/CommunityToolkit/Tooling-Windows-Submodule/blob/main/MultiTarget/UseUnoWinUI.ps1) script to facilitate switching between Uno.UI and Uno.WinUI. In #1, we moved this script into a submodule. ## Problem After the move...

dev loop ➰
regression

We're not using our centralized versions in the UWP Base Props file here: https://github.com/CommunityToolkit/Labs-Windows/blob/e6389b00e04160a71e56b409e7fc8cb14ce6fcdf/common/Labs.Uwp.Base.props#L5-L9 From: https://github.com/CommunityToolkit/Labs-Windows/blob/e6389b00e04160a71e56b409e7fc8cb14ce6fcdf/common/Labs.TargetFrameworks.props#L3 (Also, shouldn't this be Target vs. Min?) This also appears here: https://github.com/CommunityToolkit/Labs-Windows/blob/e6389b00e04160a71e56b409e7fc8cb14ce6fcdf/common/Labs.MultiTarget.props#L27-L36 Along with...

enhancement
build :fire:

### Describe the bug Right now we run it from the root, but it lives in the root. Since we have it in tooling now, we should better utilize it....

enhancement
build :fire:
CI/pipeline 🔬

from: https://github.com/CommunityToolkit/Tooling-Submodule/actions/runs/4421712339/jobs/7752798063 ![image](https://user-images.githubusercontent.com/24302614/225193847-7f956b63-fb03-4716-ae24-2250748d3144.png) Instead currently this sat for over an hour spinning without showing output... oops Low-pri right now, but wanted to track for future.

good first issue
help wanted
build :fire:
CI/pipeline 🔬

Related CommunityToolkit/Labs-Windows#37, CommunityToolkit/Labs-Windows#88 _Improvement to workaround for this Uno issue_: https://github.com/unoplatform/uno/issues/8618 - If the Uno issue gets resolved, this work doesn't need to be done and we can clean-up our...

enhancement
build :fire:
external :arrow_heading_up:
Uno

### Describe the bug Our tooling requires an enum from [CommunityToolkit.Tooling.SampleGen](https://github.com/CommunityToolkit/Labs-Windows/blob/2e2f317775ec51d0422b2564ad637538bbb94ddf/common/CommunityToolkit.Tooling.SampleGen/ToolkitSampleCategory.cs) to function. Since the tooling is being shared between multiple repositories, this data needs to be dynamic. Categories and...

bug :bug:
dev loop ➰