drewrip / bigleague Goto Github PK

The "playoffs" in our bigleague will be some kind of configurable bracket. We want to display a bracket based on the projected top finishers in the league.

This will require knowledge of the NFL state, specifically which week in the league it is.

There are many basic settings that should be easily accessible and configurable. For instance, the address and port of the database, credentials for the database, max numbers of connections to the database, and details about the size of the bracket.

We need to decide on the format of the config file, and take out the hard coded values that are currently used.

Bigleague has a module, db, for common functionality and interactions with the Postgres database. This is becoming difficult to maintain and difficult to abstract just using tokio_postgres. Before introducing too much more complex behavior, this should really be rewritten to be more generic and safe, or use something like Diesel. My current plan is to implement Diesel.

The Sleeper API allows to grab a user's matchup for a given week with the endpoint:

GET https://api.sleeper.app/v1/league/<league_id>/matchups/<week>

Their documentation on this endpoint can be found here.

It would be nice to show a users future matchups and what the scores for their players.

In order to display the current week on the standings page, and correctly track the bracket in the future we need to know the state of the NFL season. This means we need to add a table to the DB and ensure we update the state regularly.

See the Sleeper docs for information about this query: https://docs.sleeper.com/#get-nfl-state

$ curl "https://api.sleeper.app/v1/state/nfl"

{
  "week": 2, // week
  "season_type": "regular", // pre, post, regular
  "season_start_date": "2020-09-10", // regular season start
  "season": "2020", // current season
  "previous_season": "2019",
  "leg": 2, // week of regular season
  "league_season": "2021", // active season for leagues
  "league_create_season": "2021", // flips in December
  "display_week": 3 // Which week to display in UI, can be different than week
}