liquid-development/game-tracker
3
0
Fork 0
Code Issues 13 Pull Requests 5 Actions Releases 1 Activity

Konsistenzfehler in JSON vermeiden #70

New Issue
Closed
opened 2025-11-24 15:46:52 +00:00 by flixcoo · 2 comments
flixcoo commented 2025-11-24 15:46:52 +00:00
Owner
Copy Link

Feature

Beschreibung

Um Konsistenzfehler zu vermeiden, sollen in der JSON die Game-Attribute group, player winner dahingehend verändert werden, dass statt der Objekte nur die jeweiligen Gruppen- und Spieler-IDs gespeichert werden. Dies dient dazu, in der JSON keine redundanten Daten zu speichern.

# Feature ## Beschreibung Um Konsistenzfehler zu vermeiden, sollen in der JSON die `Game`-Attribute `group`, `player` `winner` dahingehend verändert werden, dass statt der Objekte nur die jeweiligen Gruppen- und Spieler-IDs gespeichert werden. Dies dient dazu, in der JSON keine redundanten Daten zu speichern.
flixcoo added the
Workflow
Backlog
4
Priority
Medium
3
 labels 2025-11-24 15:46:52 +00:00
gelbeinhalb added this to the Minimum Viable Product (MVP) milestone 2025-11-27 15:53:36 +00:00
flixcoo added
Layer
Full Stack
Task
Enhancement
 and removed
Workflow
Backlog
4
 labels 2025-12-02 17:31:30 +00:00
gelbeinhalb was assigned by flixcoo 2025-12-02 17:31:33 +00:00
gelbeinhalb commented 2025-12-06 10:08:02 +00:00
Owner
Copy Link

Soll ich nur das example-data json ändern, oder auch wie das im code importiert wird?

Wahrscheinlich beides oder?

Soll ich nur das example-data json ändern, oder auch wie das im code importiert wird? Wahrscheinlich beides oder?
flixcoo commented 2025-12-06 16:40:34 +00:00
Author
Owner
Copy Link

Soll ich nur das example-data json ändern, oder auch wie das im code importiert wird?

Wahrscheinlich beides oder?

Ja beides

> Soll ich nur das example-data json ändern, oder auch wie das im code importiert wird? > > Wahrscheinlich beides oder? Ja beides
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Duplicate
This issue or pull request already exists
Layer
BE
Issues/PRs related to the backend
Layer
DB
Issues/PRs related to the database
Layer
FE
Issues/PRs related to the frontend
Layer
Full Stack
Issues/PRs spanning multiple layers (frontend, backend, database)
PR
In Review
1
Pull Request that is reviewed
PR
Ready for Review
2
Pull Requests which are ready to be reviewed
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Task
Bug
Reports of unexpected behavior or defects in existing functionality.
Task
Documentation
Tasks related to improving or adding documentation (READMEs, code comments, guides).
Task
Enhancement
Improvements or optimizations to existing features (non-breaking changes).
Task
Feature
Requests for new functionality or significant additions to the project.
Task
Refactoring
Task
Setup
Tasks related to project configuration, tooling, or infrastructure.
Task
Testing
Issue or pull request related to testing
Workflow
Abandoned
4
Somebody has started to work on this but abandoned work
Workflow
Backlog
4
Issues/PRs that are acknowledged but not being actively worked on yet.
Workflow
In Progress
3
Issues/PRs currently being actively worked on.
Workflow
On Hold
3
Issues/PRs temporarily being paused or blocked.
Workflow
Won't Fix
5
This issue won't be fixed
No Label
Layer
Full Stack
Priority
Medium
3
Task
Enhancement
Milestone
No items
No Milestone Minimum Viable Product (MVP)
Assignees
Clear assignees
flixcoo gelbeinhalb sneeex
No Assignees gelbeinhalb
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: liquid-development/game-tracker#70
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?