supercontest.views.schedules

The schedules blueprint is the collection of the routes that act as ingresses for scheduled logic.

Module Attributes

The toplevel blueprint for endpoints that trigger scheduled tasks.

Functions

`commit_lines_route`	Entry point for scheduled behavior to fetch/commit lines when they open.
`commit_scores_route`	Entry point for scheduled behavior to check/commit live game scores.
`email_all_picks_route`	Entry point for scheduled behavior to email all picks after lockdown.
`email_unfinished_pickers_route`	Entry point for scheduled behavior to (before lockdown) reminder users who haven't picked.

supercontest.views.schedules.commit_lines_route() → Response

Entry point for scheduled behavior to fetch/commit lines when they open.

Returns:: 200 if lines were committed. 304 if all is well, you don’t need to commit lines. 500 if there was an error in the line fetch/commit attempt.

supercontest.views.schedules.commit_scores_route() → Response

Entry point for scheduled behavior to check/commit live game scores.

Returns:: 200 if scores were committed. 304 if all is well, you don’t need to commit scores. 500 if there was an error in the score fetch/commit attempt.

supercontest.views.schedules.email_all_picks_route() → Response

Entry point for scheduled behavior to email all picks after lockdown.

Returns:: 200 if the email was sent. 304 if all is well, you don’t need to send the email. 500 if there was an error in the attempt.

supercontest.views.schedules.email_unfinished_pickers_route() → Response

Entry point for scheduled behavior to (before lockdown) reminder users who haven’t picked.

Returns:: 200 if the email was sent. 304 if all is well, you don’t need to send the email. 500 if there was an error in the attempt.

supercontest.views.schedules.schedules_blueprint = <Blueprint 'schedules'>: The toplevel blueprint for endpoints that trigger scheduled tasks.