allow deactivating recipes #1848
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… the initial load
…n be fetched from the possible storage backend
4ee44b0 to
6e3142a
Compare
Tim-Linschoten
approved these changes
Mar 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds active/inactive recipes functionality to baker, deactivation triggered by a button in the developer dashboard. This feature will potentially improve the developer dashboard initial load performance when there are lots of test, legacy, obsolete recipes created during development.
After a recipe flagged as inactive, it disappears from the developer dashboard, but still can be reactivated through any bake call, or any call which requires the CompiledRecipe, like firing an event, adding recipe, etc.