Add reusable AI guidance and React package catalog
This commit is contained in:
@@ -0,0 +1,15 @@
|
||||
---
|
||||
name: maui-change
|
||||
description: Change the shared SacsMobileMaui project and validate its Sandtrap or Sandalwood consumers; not a workflow for unrelated MAUI apps.
|
||||
---
|
||||
|
||||
# Shared SacsMobileMaui Change
|
||||
|
||||
Use this workflow only for `SacsMobileMaui` and its Sandtrap or Sandalwood consumers. For another MAUI application, follow that repository's own instructions.
|
||||
|
||||
1. Read Common's `AGENTS.md`, shared trackers, and `SacsMobileMaui/docs/README.md`, `topics.md`, and `component-reviews.md`. Read consumer guidance and trackers if an app is in scope.
|
||||
2. Check status in every affected repository before editing. Keep shared-library findings in Common or `SacsMobileMaui` trackers and link to them from consumer trackers.
|
||||
3. Separate platform-independent logic from MAUI and native-handler behavior where the existing design permits. Use focused ordinary NUnit tests for logic that does not require a MAUI host; use the established MAUI host for dispatcher, dialog, and UI-dependent tests.
|
||||
4. Build the affected target framework and solution where the installed MAUI workloads permit. Windows can validate Windows and Android targets; Apple targets need a compatible Mac and Xcode. Report workload/runtime-pack failures separately from source errors.
|
||||
5. When a shared API changes, inspect active consumer call sites and validate those consumers. Do not edit consumer repositories unless they are in the requested scope.
|
||||
6. Update the MAUI and Common trackers with the tested targets, outcomes, and remaining platform limits.
|
||||
Reference in New Issue
Block a user