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

Winner soll Player-Objekt sein #50

New Issue
Closed
opened 2025-11-22 22:29:53 +00:00 by flixcoo · 0 comments
flixcoo commented 2025-11-22 22:29:53 +00:00
Owner
Copy Link

Feature

Beschreibung

Das winner Attribut des Games-Klasse soll ein Player-Objekt werden, um weitere Datenbankzugriffe zu vermeiden.

Vorgeschlagene Lösung

Um dies umzusetzen müssen folgende Dinge beachtet werden:

  • Die Methoden in GameDao müssen den ID-String in ein Player-Objekt umwandeln
  • Das winner-Attribut der Game-Klasse muss angepasst werden
# Feature ## Beschreibung Das `winner` Attribut des `Games`-Klasse soll ein `Player`-Objekt werden, um weitere Datenbankzugriffe zu vermeiden. ## Vorgeschlagene Lösung Um dies umzusetzen müssen folgende Dinge beachtet werden: - Die Methoden in `GameDao` müssen den ID-String in ein Player-Objekt umwandeln - Das `winner`-Attribut der `Game`-Klasse muss angepasst werden
flixcoo added this to the Minimum Viable Product (MVP) milestone 2025-11-22 22:29:53 +00:00
flixcoo added the
Task
Feature
Priority
High
2
Layer
DB
 labels 2025-11-22 22:29:53 +00:00
sneeex added a new dependency 2025-11-22 22:53:50 +00:00
#46 HomeView Mock-Daten entfernen
sneeex added a new dependency 2025-11-22 22:58:28 +00:00
#51 HomeView Mock-Daten entfernen
flixcoo added reference feature/50-winner-soll-player-objekt-sein 2025-11-23 00:16:08 +00:00
Sign in to join this conversation.
feature/50-winner-soll-player-objekt-sein
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
Milestone
No items
No Milestone Minimum Viable Product (MVP)
Assignees
Clear assignees
flixcoo gelbeinhalb sneeex
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#46 HomeView Mock-Daten entfernen
liquid-development/game-tracker
#51 HomeView Mock-Daten entfernen
liquid-development/game-tracker
Reference: liquid-development/game-tracker#50
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?