[Feature] NuGet button in sample app linking to NuGet package containing feature

[marcelwgn]

Describe the problem this feature would solve

Let's assume I am new to the whole WCT world. I find a cool helper inside the WCT Sample app. Now I want to add it to my app. I could try to find the information inside the docs, however beside the namespace it does not tell me the actual package I should use to get the feature. So I am now left with guessing what package to use or have to google it.

Describe the solution

Having a small NuGet button next to the GitHub button that I can use to open the packages NuGet page that contains the feature would make this a lot easier.

Describe alternatives you've considered

Adding the information to the docs makes sense, however it will probably get overlooked.

Additional context & Screenshots

Hello, 'chingucoding! 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!

[Kyaa-dost]

That sounds like a fantastic idea! @chingucoding is that something you are willing to work on and create a PR?

@michael-hawker what do you think? ⬆️

[marcelwgn]

Sure, I can work on this ☺

Question would be how we solve this the best. I was thinking about adding an entry to the samples.json. Does that seem reasonable to store what which NuGet package should be opened for every feature?

[Kyaa-dost]

@chingucoding I appreciate you taking an initiative in this area as this upcoming release is all about restructuring, improving documentation, sample app, workflow, etc.

Great question and correct that's exactly what my first thought was when you mentioned this feature. Let's see if other community members have any input in this area 🚀

[michael-hawker]

@chingucoding do you think we need to add metadata for it? Couldn't we detect the assembly from a type? (Though I guess we don't necessarily tie samples to types of the controls...) 🤔

[marcelwgn]

I think it would be more solid that way. If you try to generate the NuGet package URL from the assembly there might be slight oddities in it and then it won't work for some controls. Having the URL in there would be a safe way.