Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notify when close the front of line #341

Open
ekcom opened this issue Oct 19, 2023 · 0 comments
Open

Notify when close the front of line #341

ekcom opened this issue Oct 19, 2023 · 0 comments

Comments

@ekcom
Copy link

ekcom commented Oct 19, 2023

[Feature request]

Notify the user when there are a given number of people ahead of them in line.

This has the use case of letting people know when they are next up so that they can be prepared, especially if they have been waiting a while.

I've made a simple gist which periodically checks whenever the number of people in line has been updated and sends a notification to the user when they are a set number of spots away.
Of course, this would be better integrated into the Queue by checking directly after the relevant sockets message. This injected script is a merely a proof-of-concept.

Ideally, this would be a user-customizable setting so that people could turn this notification off if desired while leaving the "you are being helped now" notification enabled.
Also, customization on how many people out before getting the notification. E.g., some queues move faster and someone might want to be notified five people away while another person might just want to be notified when they are one spot away from being helped.

I'm not sure if this service is storing any persistent user data itself (it seems like most is authentication and directory information from Shibboleth), so this last customizable setting feature may not be feasible.
Simply using localStorage may be a possibility

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant