Canning json file #36718
Merged
Canning json file #36718
Conversation
This file contains 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
catchup to cleverraven
Moved canning pot and can sealer required recipes to canned.json. Leave pickled items in food.json.
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.
Summary
SUMMARY: Content "Move canned food recipes to separate json"
Purpose of change
Recipe_food was 7600 lines. Canned goods made up 1300 of those lines and weren't coherently arranged. Sometimes the canned good was hundreds of lines away from it's non canned partner recipe.
Describe the solution
Removed 1300 lines of canned recipes from recipe_food.json to canned.json in the food folder similar to brewing dry and dairy products. This makes it easier to compare existing/future recipes for "can this be canned?" and "has this already been canned?
Describe alternatives you've considered
None
Testing
none
Additional context