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

Fehlende Methoden für Games Datenbank inplementieren #74

New Issue
Closed
opened 2025-11-25 16:19:59 +00:00 by sneeex · 1 comment
sneeex commented 2025-11-25 16:19:59 +00:00
Owner
Copy Link

Feature

Beschreibung

Aktuell Fehlen noch einige Methode um die einzelnen Games zu verändern.

Vorgeschlagene Lösung

Methoden für folgende Usecases sollen implementiert werden:

  • SetWinner (vielleicht auch einfach wenn man SetWinner macht und einer Vorhanden ist updaten, also set und update zusammen)
  • UpdateWinner
  • UpdatePlayers
  • UpdateGroup
  • UpdateName
  • ... (ist noch weiteres Nötig?)
# Feature ## Beschreibung Aktuell Fehlen noch einige Methode um die einzelnen Games zu verändern. ## Vorgeschlagene Lösung Methoden für folgende Usecases sollen implementiert werden: - SetWinner (vielleicht auch einfach wenn man SetWinner macht und einer Vorhanden ist updaten, also set und update zusammen) - UpdateWinner - UpdatePlayers - UpdateGroup - UpdateName - ... (ist noch weiteres Nötig?)
sneeex added this to the Minimum Viable Product (MVP) milestone 2025-11-25 16:19:59 +00:00
sneeex added the
Priority
High
2
Layer
FE
 labels 2025-11-25 16:19:59 +00:00
flixcoo was assigned by sneeex 2025-11-25 16:19:59 +00:00
sneeex commented 2025-11-25 16:20:17 +00:00
Author
Owner
Copy Link

@liquid-development/Owners noch weitere Sachen nötig?

@liquid-development/Owners noch weitere Sachen nötig?
sneeex added a new dependency 2025-11-25 16:20:27 +00:00
#62 GameResultView erstellen
flixcoo added
Layer
DB
 and removed
Layer
FE
 labels 2025-11-25 16:28:38 +00:00
flixcoo added the
Workflow
In Progress
3
Task
Feature
 labels 2025-11-26 12:27:03 +00:00
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
DB
Priority
High
2
Task
Feature
Workflow
In Progress
3
Milestone
No items
No Milestone Minimum Viable Product (MVP)
Assignees
Clear assignees
flixcoo gelbeinhalb sneeex
No Assignees flixcoo
1 Participants
Notifications
Due Date
No due date set.
Blocks
#62 GameResultView erstellen
liquid-development/game-tracker
Reference: liquid-development/game-tracker#74
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?