[Feature] Use Source Generators to generate "DesignTools" projects' sources

[Nirmal4G]

Describe the problem this feature would solve

Manually making changes to "DesignTools" projects whenever there are changes to Controls is hard.

Describe the solution

Generate "DesignTools" project sources using source generators.

Describe alternatives you've considered

Continue manually writing "DesignTools" metadata source based on Controls' typedata or atleast generate typedata through T4 templates based on Controls' type info.

Additional context & Screenshots

TBA

[ghost]

Hello, 'Nirmal4G! Thanks for submitting a new feature request. I've automatically added a vote 👍 reaction to help get things started. Other community members can vote to help us prioritize this feature in the future!

[michael-hawker]

Yeah, this would be pretty epic or if we could just use T4 templates or something.

I was thinking that it'd be cool if we could just annotate properties in the code with attributes like:

[Category("Layout")]
public HorizontalAlignment ...

[Nirmal4G]

@LalithaNadimpalli This doesn't need to be a discussion. Why convert it?

[Arlodotexe]

The toolkit is moving towards using Issues exclusively for problems/bugs, and Discussions for feature requests.

[Nirmal4G]

I see, then it's fine. But why need to convert existing ones?

Github doesn't migrate while preserving the issue number. Many complained about this. So, We could wait until they support migrating with the existing issue number.

This just creates a duplicate issue number.