googleforgames / googleforgames/open-match
Support Ticket ID from user
- Dominant language
- Go
- Stars
- 3.4k
- Forks
- 359
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Based on https://github.com/googleforgames/open-match/blob/6f46731b156f5ada463b309e0a35774b11255323/internal/app/frontend/frontend_service.go#L50, a new TicketId is always created for a new ticket. But in our use case, we already have a unique playerId that can be used for this purpose. It will be great that we can use playerId so that we do not need to add logic to check whether there is already duplicate ticket created for the same player before create a new ticket.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
A user provided ID can be used as TicketId for a new created ticket. When the ID is duplicate in Redis, Open Match FrontEnd can provide 2 options, which is configurable by the user:
- Fail the request and return an error message with clear reason
- Overwrite the existing ticket with the new ticket
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Assessment
This issue has not been assessed yet.