arctos6135 / scouting-database Goto Github PK

Currently, all the tabs have this big html table that does the exact same thing for all of them. We have a tag that displays arbitrary objects in a table, make them all use it.

Self explanatory

Preferably done by Wednesday August the 7th.

Both NMA and ScoutingOutput have a toggle for whether they refer to data from all events or the current one. They use the same piece of Strategy.js' state for this, and should always do the same thing, but the checkboxes which control specific_scouting_output's value can appear different to the user. It's possible that they also become unaligned with their labelling.
Confirm that this isn't happening, and make them consistent to each other and what a user would expect. Possibly move this checkbox to the header.

It's good to know when a query has finished or whether a query is still running.

Sometimes when the outcome tables are completely empty, Orion returns nothing and it's hard to tell whether it's broken or just ignorant. Make it say something useful instead.

• colour code red/blue
• indicate teams with noteworthy attributes (pushable, ...)(currently impossible, data not stored)
• separate sandstorm/teleop (relevant only to D:DS)

Currently relies on denormalized_schedule, creating massive slowness. Find another way to get alliance partners and opponents

Currently only last match number works, that's not ideal

In some tabs (specifically, Next Match and Data Spitter), the headers for the table will appear once you select an event but disappear after a short time.

To reproduce this, start the app and quickly switch to the "Next Match" tab (or "Data Spitter") and select an event code. The headers for the table of data will pop up but disappear after a few seconds.

The expected response is that no headers should be shown unless both an event code and a next match number/team to data spit are selected, i.e. only when there's actual data to show alongside the headers.

Because this only works if you do it quickly after startup and disappears after a few seconds might mean it's something to do with the refresh() function that updates stuff every once in a while. I also wonder what the criteria is for showing the headers of the table?

(Try and fix this on a new branch. There might be multiple ways of solving this, just pick one that works. If you just can't solve this after giving it a day or two, you can ask me for more hints)

Currently, the database invents which teams are in which drive stations. Make it based on facts.

at minimum, add a page of team's robot photos.
Ideally, add these photos to nma and data spitter, as well as links in scouting output