-
Notifications
You must be signed in to change notification settings - Fork 4
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
Feature/recipe scraper #127
base: master
Are you sure you want to change the base?
Conversation
I think a possible idea is instead of placing ingredient data here. We should just map to ingredient IDs within the other service. Can we parse the ingredient list into something workable by the ingredient service, and then the service returns a list of new or existing IDs? @no-or @narendrasss |
Yeah that was the original plan, but we thought to use the same seeded db for the time being since the ingredient service is still being worked on. We can refactor it to an endpoint at a later time. |
No description provided.