Skip to content

Support for hits editing frontend #32

@Timtam

Description

@Timtam

Summary

We want to be able to edit your own hits in the frontend, allowing every instance to have their own set of hits, as well as making hit contributions easier.
This however is a huge undertaking, as it requires alot of useful, but time-consuming maintenance and rewriting steps.

This is a loose list of tasks that need to be done. For everything that has already been put into shape and opened as an issue, see below.

  • hits should validate wether their link / id is still available, and if it isn't, they should be marked as "needs fixing"
    • hits can be marked as "needs fixing" with a message on what needs to be done
    • maybe do that when they get selected and played in a game?

Motivation

Currently, all hits are maintained inside an Excel sheet, which gets saved as CSV and can then be imported into the codebase. However, this Excel sheet only lives at @Timtam 's place and thus contributions are hard to maintain. Also editing inside the Excel sheet is annoying too as it doesn't really allow us to maintain hits included in multiple packs very well.

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    clientA change that needs to happen within the client (TypeScript/React, HTML, CSS etc.)enhancementNew feature or requestserverA change that needs to happen within the server (Rust, Rocket etc.)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions