cssuob / society-voting Goto Github PK

what the fuck is this

The schema should not look like this

but instead more like this

Ability for admin to be able to:

• rename people without deleting them
• lock a users name to prevent them from changing it themselves

Because it'd be nice to know why users go missing if they go missing

Blocked on #20

See title basically.

The user and election deletion buttons and the election start button do not confirm with the user that this is what they intent to do, which could probably lead to some unintended deletions.

Note to self to sort this at some point in the future

Currently this could be done in a really scuffed way by manually adding candidates of "Yes" and "No" but would be good to have this work natively

The correct file extension for yaml files is .yaml rather than .yml (https://stackoverflow.com/a/54265316/14403974)

gg @luckystar365

basically:

• Make the entire row clickable as a button

and

• Highlight the currently selected election

I can’t seem to upload the video here from my phone, but here is the bug:

https://media.discordapp.net/attachments/1166445035961716736/1168312911853256875/RPReplay_Final1698617893.mov?ex=65514f30&is=653eda30&hm=594e0c63ede3c9d02745f6bc9e77b8b5fc238f7b01c01ec456e6c655b5fbf61f&

From a user's perspective a password for this kind of thing seems weird. I completely understand it's cos of user registration, but is there a better way of doing login like just from a single session cookie? (especially when all users will be deleted between voting events) For example VoxVote only requires a name.

Is it possible to display the results of the previous elections on the page too?

title

Allow individual user accounts to be set as administrators to aid in creating a paper trail of actions taken

The styling designed by @Vishwas-Adiga should also be used for the login page

It would be useful for users to recieve an withi-site toast notification for account related events (E.g. successful login, successful name change, successful account creation)

This is because there is no button to do so in the UI - this works fine on the backend.

Session tokens are currently generated using a key that is generated a program start, meaning session tokens are not valid between restarts.

In the case of needing to restart the platform mid-AGM (like at the Nov EGM) it would be good to not need to get everybody to refresh their pages and sign in again.

Lots of people were getting told to "Slow down!" during voting

This is a sign that I have given up trying to work out where the resource leak is.

For this issue to be closed, the presenter mode will also need to refresh itself

Soft fails without an error message as opposed to hard failing and crashing the program.

See title - needs reproducing and debugging.