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

Kennzeichnung für doppelte Spielernamen #182

New Issue
Open
opened 2026-01-21 14:28:46 +00:00 by flixcoo · 0 comments
flixcoo commented 2026-01-21 14:28:46 +00:00
Owner
Copy Link

Aktuelles Verhalten

Spieler mit gleichen Namen tauchen in der UI als der selbe Spieler auf bzw. sind visuell nicht voneinander zu unterscheiden.

Vorgeschlagene Verbesserung

Wenn Spieler mit gleichen Namen existieren sollen diese mit einem Ganzzahl-Tag (e.g. #1, #2) ausgestattet werden. Die Tags orientieren sich am Erstelldatum.

Zugehörige Issues

No response

### Aktuelles Verhalten Spieler mit gleichen Namen tauchen in der UI als der selbe Spieler auf bzw. sind visuell nicht voneinander zu unterscheiden. ### Vorgeschlagene Verbesserung Wenn Spieler mit gleichen Namen existieren sollen diese mit einem Ganzzahl-Tag (e.g. `#1`, `#2`) ausgestattet werden. Die Tags orientieren sich am Erstelldatum. ### Zugehörige Issues _No response_
flixcoo added this to the Alpha milestone 2026-01-21 14:28:46 +00:00
flixcoo added the
Task
Enhancement
Priority
Low
4
Layer
FE
 labels 2026-01-21 14:28:46 +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
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
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
FE
Priority
Low
4
Task
Enhancement
Milestone
No items
No Milestone Alpha
Assignees
Clear assignees
actions flixcoo gelbeinhalb sneeex
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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