We've released v1.2.0 of the Queue! This release includes dark mode, API access tokens, and a bunch of smaller bug fixes and enhancements. Read on to learn more!
If you've logged into the queue recently, you may have noticed there is a new toggle near the logout button. Clicking this will enable our new highly sought-after feature - dark mode! We hope being on the queue will no longer burn out your eyes (just your soul).
The philosophy behind the Queue has always been to make it programmable and developer-first, which could enable integrations with services like PrairieLearn and the CBTF. To bring us closer to that goal, we recently rolled out programmatic access control, and now: access tokens!
Access tokens can be managed through the user settings page (which can be accessed by clicking on your name, next to the logout button). These tokens allow you to access the API as if you were logged in through the website. As such, you should be careful about keeping your tokens private. With an access token, you can:
- Add yourself to the queue
- List all questions on a specific queue
- Manage access tokens
- Do anything else the web interface can do
Authenticating through an access token is simple: just append
?private_token=... to the URL or use the
For specifics about the API, check out the API docs.
Since the v1.0.0 release, there have been a few other behind-the-scenes improvements and bug fixes:
- Disconnecting from the websocket will no longer cause a 404 page to appear; the app will now automatically try to reconnect and will show status updates to users.
- A race condition with realtime updates was discovered and fixed.
- There's a new admin-facing page for admins to manage the list of other admins. No more manual database queries to add or remove queue administrators!
- An issue where the course page would double-render when loading has been fixed.
Check out the changelog on GitHub to see the full list of recent changes!
As always, a reminder that the Queue is open source! We rely on contributions from users across the university to bring new features and improvements to the Queue. If you have a suggestion for a new feature, you can start a discussion on a GitHub issue. Or, if you want to start contributing, you can join the Illinois OSS Slack to work with other Queue developers.