[kusutoriクスとり (kusutori)]

Summary

Add the missing typed ResourceBuilder.Set overloads for Thickness, FontWeight, FontFamily, bool, Color, and GridLength, completing the common non-brush styling surface described by spec 015.

• Preserve literal value types and existing color-string/brush/ThemeRef behavior; no generic catch-all or int overload.
• Add unit tests and native WinUI fixtures covering typed values, mount/update/removal, control reuse, unmanaged-resource preservation, and BreadcrumbBar usage.
• Update the styling guide through its template and regenerate both API index copies.

Linked issue / spec

Fixes #1369

Related: spec 015.

Test plan

• Release x64 builds of the unit-test project and native selftest host.
• LightweightStylingTests: 20 passed, 0 failed/skipped.
• TypedResource_ WinUI selftests: 2 fixtures, 27 checks passed.
• Temporarily no-op the Thickness overload: its targeted test failed; restore the implementation and rerun the 20-test class successfully.
• Compile the styling topic and verify the two generated API indexes are identical.
• Downstream Tonarink Release x64 publish and Debug mur devtools inspection: native BreadcrumbBar resources retain the expected types and values.

Validation was focused on this change; the full solution/suites, MSIX, and Native AOT were not run locally. The unit-test build reported the upstream test graph's existing NU1902/NU1903 warnings for System.Security.Cryptography.Pkcs 9.0.6; package versions and auditing settings were not changed.

Risk / breaking changes

Additive overloads only. Existing integer arguments still select double; string arguments still create brushes. Reconciliation and theme resolution are unchanged.

[Alexandre Zollinger Chohfi (azchohfi)]

Thanks for this, the typed overloads fill a real gap. A few things to address inline: FontFamily equality across renders, making the Color overload's intent explicit, proving template consumption in the BreadcrumbBar fixture, and syncing the design specs plus a FontFamily example in the guide.

[kusutoriクスとり (kusutori)]

Thanks Alexandre Zollinger Chohfi (@azchohfi) for the detailed feedback! Addressed the review in 51dfc4f:

• Compare FontFamily literals by Source, with equal/different checks using freshly allocated families, plus value-equality checks for the five new value types
• Rename the literal-color overload to SetColor, keeping the distinction from brush resources explicit in the API and documentation
• Probe the rendered BreadcrumbBar label and template chevron after layout, alongside an unstyled baseline, rather than only reading the resource dictionary
• Update the design specs, implementation checklist, generated guide and both API indexes, including an explicit new FontFamily(...) example

Validation: Release host build passed with no warnings/errors; 21 LightweightStyling unit tests and the targeted TypedResource selftests passed. Deliberately disabling the Thickness/FontWeight setters and FontFamily equality caused the relevant checks to fail; the restored implementation passed again. Styling documentation compiles and both API indexes match.

Existing dependency warnings in the unit-test project and unresolved documentation cref warnings remain.

Please let me know if anything else needs adjusting.

[kusutoriクスとり (kusutori)]

Thanks for catching both issues! Fixed in dee803a:

• Use a Button, which consumes ContentControlThemeFontFamily, instead of a TextBlock
• Move the example into the styling doc app's font-family-resource snippet and reference it from the template
• Recompile docs/guide/styling.md

The doc pipeline built the styling app and compiled the topic successfully. All 15 InlineSnippetLedgerTests also passed, including the check that rejected the previous inline example.

[Alexandre Zollinger Chohfi (azchohfi)]

Thanks kusutoriクスとり (@kusutori)! All review feedback is addressed and CI is green. LGTM.