FIRST-Tech-Challenge / FIRST-Tech-Challenge/scorekeeper

Create reusable alias for the event code in the URL so reusable bookmarks could be used.

Open
#839 1 comment 4 reactions 0 assignees View on GitHub
Local
Dominant language
No language data
Stars
110
Forks
26
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
As an FTA, I'm always frustrated at the beginning of the event when I have to change the URLs on all the devices to the event-specific one.

**Describe the solution you'd like**
I would like an aliased event code in the URL instead of having the event code change for every event. For example, if I use a laptop to view the 2-column display of the inspection status for the 'nj20250216' event, I use the URL http://localhost/event/nj20250216/status/proj/2/ . Next week, I have to change the URL to http://localhost/event/nj20250223/status/proj/2/ . I'd rather have a URL such as http://localhost/event/current/status/proj/2/ which I could bookmark and use for every event. The scoring system would keep track of what event was most recently activated and resolve 'current' to that event.

**Describe alternatives you've considered**
No alternatives have been seriously considered, but I could write a simple web app that stores the current event code and listens for URLs and redirects to the scoring system URL for that event code.

**Additional context**
Managing one or two URLs isn't too hard, but there are many places where event-specific URLs are used. For example, for our streaming / projection setup, four or five URLs are stored an used as 'Sources' of information to be displayed. Failing to update one means the information from a previous event is displayed.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.