BREAD5940 / BREAD5940/frc-scouting
Add more categories for failure
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Per Team 5940 scouting leadership we should track robots that don't show up or have communication issues, in addition to robots that have mechanical or electrical failures (`borked`) and robots that must be disabled (`emergencyStopped`).
This will involve modifying SQL schemas (database migrations of some sort), but the `MatchData` code to be modified is as follows: https://github.com/BREAD5940/frc-scouting/blob/d1b8a2ac54db38cfd447eff80f64d6bc34b2e9c7/src/match.ts#L27-L37
Contributor guide
Research direction
Start with src/match.ts lines 27-37 to understand the existing borked and emergencyStopped failure categories. Then inspect the repository's SQL schema and migration setup. Done means adding categories for robots that do not show up and robots with communication issues, with the MatchData handling and database schema kept consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql, typescript
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100