Hello,

We are moving the request to unplanned in order to gain more popularity. We are evaluating the benefits of the snippets and what kind of snippets would be beneficial for our customers. We would appreciate any feedback about what snippets might facilitate your experience and fasten your usage.

Regards,
Joana
Progress Telerik

Hello Steve,

Thank you for opening this request.

At this time, I am going to have to "reject" it because of the list of reasons below. If the idea does get traction with the community, we can re-evaluate its status.

In order of importance:

1. There are already web pages where you can copy and paste snippets from - our documentation. The first snippets for every component are always runnable as-is with a simple copy-paste (well, the Upload is an exception, but it is quite a special one). All other articles also contain many examples you can copy-paste, most of them self-contained within a single snippet, rarely into more than one.
   
2. What each developer would need from those snippets is highly individual. Once you see yourself using something over and over, you could either create a snippet yourself, or wrap it in a component in your app. The thing is that if we manage to provide snippets for all scenarios people need, there will be too many to use comfortably, and providing some bare minimum will not satisfy too many people either.
3. It will be a really massive effort to create and then to maintain so many code snippets, while the feature is not really popular (that's the first request in 2 years). That time and effort we would have to invest in this can provide must bigger benefits elsewhere.
4. The framework and Intellisense are slated to be able to show contextual tags only - meaning that you will see only top-level component tags, and their child tags will only show up in the context of an appropriate parent. By the time we could get to creating so many snippets (and to also look into prioritizing and implementing some sort of automation), it is likely that this feature would have landed and would provide just about the same flexibility, and other benefits.

That said, if you start creating your own snippets, you can share them with the community. For example, this repo is a good place, you can make a "snippets" folder in the "common" folder for that. If you do so, we can link it from the KB article about the toolbox.

Regards,
Marin Bratanov
Progress Telerik