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

Should we endow the API scraper/s with knowledge of the available endpoints? #69

Open
hancush opened this issue Apr 19, 2018 · 0 comments

Comments

@hancush
Copy link
Collaborator

hancush commented Apr 19, 2018

Currently, we manually build endpoint URLs, like so:

events_url = self.BASE_URL + '/events/'

It would be cool to be able to reference endpoints like self.EVENTS_URL, etc.

If we we go this direction, we ought to have a conversation about whether to include all of the endpoints, or an oft-used subset, and how to organize that knowledge amongst the base scraper and its children.

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

No branches or pull requests

1 participant