Conversation
|
Thanks for the PR — that closed out 5 placeholders. Here's the rest, grouped by file. The underlying issue isn't missing functionality — it's that several samples use placeholder or low-signal labels or lack a clear sample-level semantic title/description. That makes automated extraction fall back to generic labels like "Basic usage" or "Example N", which hurts discoverability for agents/tools. Group A — multi-instance demos with placeholder per-card contentcomponents/Segmented/samples/SegmentedBasicSample.xaml All controls:SegmentedItem still "Item 1/2/3/4" — replace with real-world labels. Group B — single-sample demos lacking a sample-level semantic title (19 files)These all have one big demo. Some DO have inner Headers (HeaderedContentControl: "Rectangle content"; SettingsExpander: "SettingsExpander", "A basic SettingsCard within...", etc.; TabbedCommandBar: "Home", "Insert", "Picture Format") but none have a sample-level title my tool can stably pick up, so we fall back to "Basic usage". Three options to fix:
components/Collections/samples/AdvancedCollectionViewSample.xaml components/Collections/samples/IncrementalLoadingCollectionSample.xaml Group C — file name hints at variant but the description is too shortThe split sample files already exist with meaningful names, but my tool's auto-derived description is just one or two words pulled from the filename. A one-sentence Description on the wrapping element (or a short comment my parser could pick up) would make these searchable. components/HeaderedControls/samples/HeaderedContentControlComplexSample.xaml ("Complex" — what kind?) |
Fixes
PR Type
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
PR Checklist
Please check if your PR fulfills the following requirements:
Other information