### Describe the bug Would be nice to convert to something like: ```cs [ToolkitSample(...)] public sealed partial class MySample : Page { [ToolkitSampleNumericOption(min: 0.0, max: 1.0)] public partial double MyRangeValue { get; set; } = 0.5; } ``` This can make it clearer to see the properties in the code-behind (and use them there) as well. ### Steps to reproduce ```text N/A ``` ### Expected behavior N/A ### Screenshots _No response_ ### Code Platform - [ ] UWP - [ ] WinAppSDK / WinUI 3 - [ ] Web Assembly (WASM) - [ ] Android - [ ] iOS - [ ] MacOS - [ ] Linux / GTK ### Windows Build Number - [ ] Windows 10 1809 (Build 17763) - [ ] Windows 10 1903 (Build 18362) - [ ] Windows 10 1909 (Build 18363) - [ ] Windows 10 2004 (Build 19041) - [ ] Windows 10 20H2 (Build 19042) - [ ] Windows 10 21H1 (Build 19043) - [ ] Windows 11 21H2 (Build 22000) - [ ] Other (specify) ### Other Windows Build number _No response_ ### App minimum and target SDK version - [ ] Windows 10, version 1809 (Build 17763) - [ ] Windows 10, version 1903 (Build 18362) - [ ] Windows 10, version 1909 (Build 18363) - [ ] Windows 10, version 2004 (Build 19041) - [ ] Other (specify) ### Other SDK version _No response_ ### Visual Studio Version _No response_ ### Visual Studio Build Number _No response_ ### Device form factor _No response_ ### Additional context _No response_ ### Help us help you Yes, but only if others can assist.
Activity
michael-hawker commentedon Nov 23, 2024
Maybe we could get away with having "Numeric" and "Bool" option as we'd be able to detect the type of the partial now too?
Arlodotexe commentedon Nov 25, 2024
The attribute parameters are different for each type.