Add recipe import from free-text ingredient lists (#7) - #49
Merged
Conversation
Mirrors the app's "Import Recipe": ingredient lines are handed to Cronometer's parser, which matches each to a database food and converts stated amounts to grams, so callers don't need food IDs up front. The import is the API's one async job -- import_recipe returns a future id and poll_async_result is polled until it attaches a result. Matched ingredients are then persisted through the existing create_recipe path. Lines the parser can't resolve are reported separately instead of failing the whole batch on create_recipe's gram validation.
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
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.
Mirrors the app's "Import Recipe": ingredient lines are handed to Cronometer's parser, which matches each to a database food and converts stated amounts to grams, so callers don't need food IDs up front.
The import is the API's one async job -- import_recipe returns a future id and poll_async_result is polled until it attaches a result. Matched ingredients are then persisted through the existing create_recipe path. Lines the parser can't resolve are reported separately instead of failing the whole batch on create_recipe's gram validation.