Skip to content
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

Open
wants to merge 34 commits into
base: master
Choose a base branch
from
Open

Feature/recipe scraper #127

wants to merge 34 commits into from

Conversation

no-or
Copy link
Contributor

@no-or no-or commented Mar 14, 2020

No description provided.

@DConnorFong
Copy link
Collaborator

DConnorFong commented Mar 14, 2020

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

@nandanmen
Copy link
Contributor

I think a possible idea is instead of placing ingredient data here. We should just map to ingredient IDs within the other service.

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants