dkutin / fantasytracker

A Yahoo! Fantasy Tracker application that allows you to see your fantasy data, your way. Made using a php backend that interacts with MySQL database to save player info and data from Yahoo! Fantasy API, with a React app frontend.

Hi there, I'm Dmitry 👋

fantasytracker's Issues

As a developer, add a file that generates the report and emails the report to the user so that the user is able to receive the data from a centralized codebase

• Create a file to generate reports,
• Email the report to the given user based on their team

Migrate Schemas from MySQL to MongoDB

Currently, this project uses a MySQL database to store data. While convenient, acquiring hosting and future improvements are made more difficult.

This task is to migrate all schemas from MySQL to MongoDB, leveraging node.js, and mongoose.

AC:

• All Schemas in created in the codebase.
• MongoDB connection set up.
• PR merged.

As a developer, change paths used in all php files to be relative paths for use in crontab

Currently, if we try to run a crontab, the auth file has improper referencing and tries to create another in the home directory. We want to change this to read the auth file we currently have in the project directory; as well as all other files.

As a developer, create a file to generate a webpage with the same report a user may get in the email so that unregistered users can see insightful player trends

As a developer, rewrite the algorithm for player rankings to include 7 day, 14 day and 30 day averages so that it provides a more accurate representation to the user

The algorithm currently ranks players based on how many free agents are better than a current roster player, if the value for a roster player is a negative and free agent is positive, a recommendation is made.

As a developer, create a file to be run by crontab that takes backups of tmp/ directory so that data is not lost if an unsuccessful request is made

Migrate ServiceCall class to use new API

AC:

• Migrate ServiceCall class to node.js / express.
• Connect to use the format of new API.
• PR merged.

As a developer, eliminate the need of saving json files by writing the result of the request to db so that JSON files are not saved to the filesystem

• Move from writeToFIle() to serialize the JSON and write to DB sorted by week and player

Convert PHP files to use Express and Node.js

Migrate FantasyAPI class to use express and node.js

AC:

• FantasyAPI can be connected to API.
• PR merged.

Refresh token causes program to return "Error" when it successfully refreshes

Change API to use more general one, so that we can build the stats ourselves

AC:

• YAHOO! Fantasy API no longer connected (Thank god.)
• Investigate and connect new API for player data (That can provide realtime stats)

As a developer, create a database schema for saving player averages across weeks and past generated reports so that unnecessary JSON files aren't stored to the user's filesystem

Currently, all player info and reports are stored in json files with a naming convention of playerid_week. Implement the database to store players by week, with their respective averages.

Reports are saved in jsons with the time they were generated. Instead, save the report for the day and time it was generated and save to database, so if a report for the day had already been generated we can query it without having to call fantasy API.

As a developer, implement a file that can be run separate to analysis that updates the database with current player values for the week, at the end of the week so that the codebase works with the most recent/accurate data of player averages

Currently, a new request is made for all data of player averages when the driver file is run. This can cause misleading data as if the driver is run in the middle of the week, player averages may not correctly reflect their stats for the entire week.

As a developer, add a script that can be run by cron to pull from git repo so that the server repo stays up to date

As a developer, rewrite the codebase to query database instead of json files so that unnecessary data isn't written to the user's files

Currently, the codebase queries JSON files saved to create a report and send an email. Rework this to query the database instead that stores these JSON files.

As a developer, add a table to the database to store user credentials and refresh token so that any requests made to the API query this

Currently, a JSON file with user credentials is stored in a JSON file under the user's consumer id. Change this to store the same information in the database in the user table.

As a developer, rework current report generation function to be an intuitive recommendation of players to add/drop so that its human readable by the end user

Currently, a string is generated by roster.php and freeagent.php to show the changes in player averages for 7 day, 14 day and 30 day (depending on the data available).