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

Support for non-Cornell Dining eateries #4

Open
willbarkoff opened this issue Nov 6, 2020 · 0 comments
Open

Support for non-Cornell Dining eateries #4

willbarkoff opened this issue Nov 6, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@willbarkoff
Copy link
Owner

Right now, the Cornell Dining API only returns information for Cornell Dining-run eateries. Others exist, some popular examples being Terrace, Temple of Zeus, and Manndible. Some of these accept BRBs, while others don't.

Eatery hardcodes these, and a similar approach would likely be ideal – potentially Foodie could offload this onto the Eatery API (it's a pretty simple GraphQL API, eatery-backend.cornellappdev.com), though that feels wrong. Potentially Foodie could just support the same format that eatery-backend does for external eateries and the JSON files could be kept in sync?

https://github.com/cuappdev/eatery-backend/blob/master/static_sources/externalEateries.json

@willbarkoff willbarkoff added the enhancement New feature or request label Nov 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant