Features

• 🛠️ Modern Admin Interface created with Svelte5 and SvelteKit
• 🏡 Create new games (also through csv upload), edit the existing ones, delete them! You have full control!
• 📝 Superforms is used to handle validation with the forms
• 🎨 Styling created using TailwindCSS and Zeit Design System
• ⌨️ 100% written in TypeScript
• 💻 Reach local the server easily with postqREST
• 🧪 Test using vitest and svelte testing library
• 🎁 ...much more

Description of the project

Following the modus operandi of other games, it was decided that eckchen needed a new admin interface where people could easily update information regarding the games. The project is managed by the team Engagement and Games.

Requirements

• Node.js
• nvm
• npm

Setup

1. Clone the repo
2. Run nvm use to install the latest lts version
3. Run npm i --force to install the required packages. As soon as Svelte 5 will become stable, we will not need --force.
4. Run npm run dev to start the dev server

Test

You can run some tests by using the following commands:

1. npm run test:unit to run all the unit tests.

To Dos

Check the main task on Jira for further information.

• Implement the Microsoft Authentication
• POST game (works but the id generation is manually done instead of through the db). Here we have the problem that when we submit the game, we are sending one only request to create the game and the questions (not yet the game_state). Since we cannot create the questions without the game_id, that is why we do the id generation manually. However, we might need to refactor to do 2 requests.
• POST questions
• Validation is required (for the moment, we can create games without questions)
• PATCH game and questions do not work as expected (they are creating instead of UPSERT) and you need to update the page to make it work.
• We have used superform in NewGameView.svelte in two forms. Do we need it also when updating game and deleting?
• DELETE game with CASCADE of the game_question and game_state
• Tests for the different views need to be written.
• beforeleave message (when clicking back in theb browser oder zueruck in the buttons so that user does not lose information if there was)
• whole logs topic (need to be discussed) + logs table sort + pagination
• adr (pr started)