-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Cake.Sitecore to blacklist #126
Add Cake.Sitecore to blacklist #126
Conversation
@Jericho if this PR is merged: Would AddinDiscoverer create a PR to add it back again? |
Then probably its fine and this PR is not required. What @gep13 said on the website it is currently listed as an addin and I wanted to avoid that addin discoverer creates a PR if we remove the file. |
In other words: does the discoverer create YAML files for recipes? Good question. Give me a few minutes I'll double check. |
Answer: no, the discoverer does not create YAML files for recipes. We only create/update YAML files for NuGet packages that have been categorized as addins (here): The import line of code is: .Where(addin => addin.Type == AddinType.Addin) Therefore, feel free to delete the YAML file for the Cake.SiteCore recipe. It will not be recreated by the dicoverer. |
This brings up an interesting question: should the discoverer actively delete YAML files for recipes? Currently we delete YAML files when an addin becomes "deprecated" or is removed from NuGet. |
Yes, I think that would be a good addition. |
In the future I would like to have recipes (and modules) listed on the website and not only addins (therefore the name switch from /addins to /extensions). But it is not implemented yet. |
In other words, you think the discoverer should not delete YAML files for recipes? If that's the case, discoverer should add/modify YAML for the recipes as well, don't you think? |
We need to first implement it on the website. Don't know yet what best design ist (same yaml structure in the same folder, a different file somewhere else, etc). |
Add Cake.Sitecore to blacklist since it is not an addin but a recipe script.
It is recognized as addin, since it contains some tools. A better way than blacklisting would be to improve detection of recipe packages.