You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should rename this repo to better represent what this repo is for. "demo-apps" is too generic.
Something like "blog-samples" would be better. Then create a folder for each platform so we can put samples for blogs covering all products. For example:
blog-samples
--- angular
--- wpf
--- etc.
However, we already have repos for samples that will be used for support and customers. For example, there is an already existing angular-samples that are to be used for runnable samples. Depending on the sample you are creating, it may be better to put the sample code in the angular-samples repo instead.
This repo may not be needed.
The text was updated successfully, but these errors were encountered:
To clarify, I used the angular samples repo as an example. I see you are adding a React sample. Of course, we would place this specific ample in a react-samples repo instead of the angular repo.
We should rename this repo to better represent what this repo is for. "demo-apps" is too generic.
Something like "blog-samples" would be better. Then create a folder for each platform so we can put samples for blogs covering all products. For example:
blog-samples
--- angular
--- wpf
--- etc.
However, we already have repos for samples that will be used for support and customers. For example, there is an already existing angular-samples that are to be used for runnable samples. Depending on the sample you are creating, it may be better to put the sample code in the angular-samples repo instead.
This repo may not be needed.
The text was updated successfully, but these errors were encountered: