Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Designing Database / Adding scoring features / Roster splitting #5

Open
rjbray915 opened this issue Mar 4, 2021 · 1 comment
Open
Assignees
Milestone

Comments

@rjbray915
Copy link
Contributor

Continue adding database fields for Players like batting average and score / game. Begin implementing features for tagging games, like pitches. Roster splitting would be nice to implement, since this is one of our major features compared to our competitors. This will likely spill into the next sprint, since it will be more important to implement tagging features first.

@rjbray915 rjbray915 self-assigned this Mar 4, 2021
@rjbray915
Copy link
Contributor Author

Worked with Taylor to add new Models for Inning, Game, Play, AtBat, and Pitch to keep track of scoring and timestamps for tagging. This was put into a separate branch and needs to be tested for Sprint 3. Now we need to link this with the frontend and get tagging going.

@rjbray915 rjbray915 added this to the Sprint 2 milestone Apr 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant