Dynamically update sports + sportsbook data #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is meant for commits made on June 16th that were mistakenly merged with
the previous PR. These commits address dynamically adding sports + sportsbook
data depending on user configuration. The idea is that the user can decide when
to update the local sports + sportsbook data instead of making 2 API calls every
time they create an instance of the
Rundownclass.cc32e7a
refresh_cached_datatoTrueon creating an instance of theRundownclass, the static data will beupdated
refresh_sportsbooksandrefresh_sportsfunctions added in order to writedata to local files
sportsandsportsbooksmethodsd79f518
use_sportsbook_namevalidator defaults to sportsbook ID if a name is notfound (if the local sportsbook data hasn't been updated)
1237cce
staticmodule withbuild_sportsbook_dictandbuild_sports_dictcreated,together with
sports.yamlandsportsbook.yamlTodo