trotFunky/FabulaVotes
1
0
Fork 0
Code Releases Packages Activity
A simple application presenting truths and allowing people to guess on their authors for an upcoming campaign of Fabula Ultima
41 commits 1 branch 8 tags 130 KiB
Find a file
trotFunky 24ab2fc5f2 vote_chart: Remove hash part of the URL 
Now that the truths have anchor links, a user could select one and send the link
directly to the truth, or refresh the page to there.
However, the local part of the URL would be used by the script to fetch the voting
data, which fail as it isn't expected by the server and is, anyway, malformed.

Remove the local hash from the URL before requesting the voting data.
2024-08-01 22:42:07 +01:00
db tag: Introduce tag system 2024-08-01 21:55:47 +01:00
src tag: Introduce tag system 2024-08-01 21:55:47 +01:00
static_files vote_chart: Remove hash part of the URL 2024-08-01 22:42:07 +01:00
templates tag: Introduce tag system 2024-08-01 21:55:47 +01:00
.gitignore v1.0: First production version 2024-07-23 21:51:42 +01:00
Cargo.lock tag: Introduce tag system 2024-08-01 21:55:47 +01:00
Cargo.toml tag: Introduce tag system 2024-08-01 21:55:47 +01:00
LICENSE.md v1.0: First production version 2024-07-23 21:51:42 +01:00
README.md README: Add forgotten frontend dependency 2024-07-30 23:34:17 +01:00
Rocket.toml v1.0: First production version 2024-07-23 21:51:42 +01:00

README.md

Fabula Votes

This web application is intended as a simple way to share Truths for an upcoming campaign of Fabula Ultima, vote and who we think wrote them and see some stats !

TODO

A list of things that could be implemented/added to the application, some of them are needed for "feature completeness" !

  • Being able to change from one week to the next
    • Create new weeks for the admin
    • Proper week redirection
      • Correctly handle non-existing week number
  • Add introduction to the weekly truths
  • Bundle static assets in the binary
  • Move the database queries to their own functions
    • Cache those results
  • Centralize Markdown parsing ?
  • Use fairings for the different elements
  • Use guards for User calls ?
  • Use SQLite Row ID for User IDs rather than regular IDs, for randomness ?
  • Split user from vote data

Dependencies

This project currently uses, for the backend :

  • Rocket, for the web application backend
  • SQLX, for database access (this is only expeceted to be used with SQLite)
  • Tera, for templating
  • Argon2, for password hashing
  • Pull_down CMark, for markdown rendering

For the frontend :

  • Chart.js, for rendering the vote graph.

License

The code present in this repository is licensed under the Mozilla Public License 2.0.