Fantasy Congress
Fantasy sports league for U.S. politics. Draft members of congress for your team, earn points weekly from their actions, and become a champion by getting the most points during the season.
Responded to emails, cleaned inbox
Ran job to update legislator's average points
Wrote thank you letters to some of the alpha participants
Got pagination working for virtual resources (weekly totals) [fc-congress-members]
3 hrs of tinkering and reading the docs
Create totals endpoint [fc-congress-members]
Finally figured out how to get weekly filterable totals of points for legislators
Reading a lot about RESTful design, how to make aggregated data and virtual resources (those that don't map directly to the DB) available
Reached out to three alpha participants about customer interviews, one already said yes!
Create custom filter for action viewset [fc-congress-members]
Moved filters to services package [fc-congress-members]
Created services package and added packages for actions and members [fc-congress-members]
Commented out old view for member actions, starting fresh with a new model viewset [fc-congress-members]
Removed old templates [fc-congress-members]
Reduced members model viewset down to the bare minimum in order to reevaluate how to implement business logic [fc-congress-members]
Moved urls for data app out of the main urls.py file and into a urls.py file in the data app [fc-congress-members]
Started refactoring the congress member app, separated views in to their own files [fc-congress-members]
Add custom exception and business logic to PATCH requests to update data about players [fc-platform]
Add get player function to league manager [fc-platform]
Run job to update changes to congress, update average legislator points [fc-congress-members]
Update data changes for team single, league edit, league single, and team edit pages [fc-platform-frontend]
Refactor function to get pending leagues [fc-platform-frontend]
