Only the API endpoints need to be implemented for this
The rough experience on the frontend should be:
As the user, I have selected the match type (how this happened is irrelevant for this issue), e.g., qualification 1, playoff 7, final 2
I also provided the video types (in our case, we can start with Program and Overhead as default video types)
The frontend makes an API request to "guess" the file name from the backend. Then one of two things happens
the backend finds (fuzzy match) a file that seems like it corresponds to this match and video type (qualification 1 - overhead, for instance, might be found in Qualification 1 Overhead.mp4)
the backend is unable to find one or more matching files. in this case, the frontend shows an error, the expected file name, and other helpful tips
Rough sketch:
Expected output:
The video filenames are available for the frontend to send to the backend with the upload request(s)
Other notes:
Include edit buttons for each video type so that if the wrong file matches, the user can edit it directly
Only the API endpoints need to be implemented for this
The rough experience on the frontend should be:
Qualification 1 Overhead.mp4
)Rough sketch:
Expected output:
Other notes: