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

Standardize tracker object / behavior #1

Closed
bcongdon opened this issue Oct 3, 2016 · 1 comment
Closed

Standardize tracker object / behavior #1

bcongdon opened this issue Oct 3, 2016 · 1 comment
Labels

Comments

@bcongdon
Copy link
Owner

bcongdon commented Oct 3, 2016

Trackers should be objects, instead of formless modules. They behave more like objects already, and it's more idiomatic to call duck-typed functions of a subclass to Tracker than to a module.

Trackers should be able to do the following:

  • Authenticate the API client
    • handleAuthentication()
  • Do some type of regular scraping function
    • scrape()
  • Do a complete 'refresh' of their object's database
    • backfill()

Trackers should be distinct from their associated models, and should only have simple CRUD tasks on the actual data.

@bcongdon
Copy link
Owner Author

bcongdon commented Oct 4, 2016

Added as of 7d6a252

@bcongdon bcongdon closed this as completed Oct 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant