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

Implementierung von multipleWinners #205

New Issue
Closed
opened 2026-05-01 07:23:09 +00:00 by flixcoo · 0 comments
flixcoo commented 2026-05-01 07:23:09 +00:00
Owner
Copy Link

Beschreibung

Für den Enum Ruleset.multipleWinners gibt es aktuell noch keine Implementierung. Für diesen soll jetzt eine neue Variante der MatchResultView erstellt werden.

Vorgeschlagene Lösung

  • Es soll ähnlich wie bei Ruleset.singleWinner eine Radio-Button Liste angezeigt werden, in welcher dann mehrere Gewinner ausgewählt werden können.
  • In der Datenbank sollen die Gewinner dann genau so wie bei singleLooser gespeichert werden.
  • Das Abgreifen der MVPs sollte ohne weitere Probleme über die Match-Klasse funktionieren

Zugehörige Issues

Knüpft an #132 an

### Beschreibung Für den Enum `Ruleset.multipleWinners` gibt es aktuell noch keine Implementierung. Für diesen soll jetzt eine neue Variante der `MatchResultView` erstellt werden. ### Vorgeschlagene Lösung - Es soll ähnlich wie bei `Ruleset.singleWinner` eine Radio-Button Liste angezeigt werden, in welcher dann mehrere Gewinner ausgewählt werden können. - In der Datenbank sollen die Gewinner dann genau so wie bei `singleLooser` gespeichert werden. - Das Abgreifen der MVPs sollte ohne weitere Probleme über die Match-Klasse funktionieren ### Zugehörige Issues Knüpft an #132 an
flixcoo added this to the Alpha milestone 2026-05-01 07:23:09 +00:00
flixcoo added the
Task
Feature
Priority
Low
4
Layer
Full Stack
 labels 2026-05-01 07:23:09 +00:00
sneeex self-assigned this 2026-05-09 11:07:35 +00:00
sneeex added reference feature/205-Implementierung-von-multipleWinners 2026-05-10 08:22:43 +00:00
Sign in to join this conversation.
feature/205-Implementierung-von-multipleWinners
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
Proposal
This issue contains a proposal for a new feature, change, or improvement. It is open for discussion and feedback before any decision is made.
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
Hotfix
Task
Refactoring
Tasks that only involve refactoring and do not add any new functionality
Task
Setup
Tasks related to project configuration, tooling, or infrastructure.
Task
Testing
Issue or pull request related to testing
Technical Debt
Issues related to code that needs to be refactored, cleaned up, or improved due to shortcuts or outdated implementations and to keep the codebase maintainable.
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
Low
4
Task
Feature
Milestone
No items
No Milestone Alpha
Assignees
Clear assignees
actions flixcoo gelbeinhalb sneeex
No Assignees sneeex
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: liquid-development/game-tracker#205
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?