- Issue created by @rkoller
- 🇺🇸United States chrisfromredfin Portland, Maine
Documenting here that the main reason for this is that the applied recipes are stored in state in "project_browser.applied_recipes"
This happens in onApply in RecipeActivator.php
So, this begs the question - what kinds of activities imply that a recipe no longer is considered "applied?" If a dependent module of a recipe is uninstalled, should that clear the state?
Thinking broader, should we even be considered the recipe as "Applied" once and for all? My understanding is recipes are idempotent anyway, so can be applied and re-applied later if need be. If that's the case, I think it would be better to store a log of applications of a recipe, and simply show in the UI that this recipe has been applied at some point in the past. Right now, in fact, I believe that once a recipe is applied through the UI, it cannot be applied again through the UI, which is limiting for what recipes are supposed to do. I think it would be nice to instead store a list of timestamps of when a recipe was applied to the site, and let people view the log?
- 🇦🇺Australia pameeela
Thinking broader, should we even be considered the recipe as "Applied" once and for all?
No, in fact, we shouldn't -- there are some recipes that should be reapplied as needed. For example, the SEO tools recipe adds fields to content types. If you add a new content type, you would want to reapply the recipe to get the same fields on the new one.
It is useful to know whether a recipe has been applied, but it shouldn't be a "final" thing.
