Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API_GetTicketData should be 6 different endpoints #2262

Open
wescopeland opened this issue Feb 25, 2024 · 0 comments
Open

API_GetTicketData should be 6 different endpoints #2262

wescopeland opened this issue Feb 25, 2024 · 0 comments
Labels
area/api-web Web API kind/enhancement New feature or request

Comments

@wescopeland
Copy link
Member

Currently, API_GetTicketData has the following routines:

  • Get details for a specific ticket by ticket ID
  • Get open tickets ordered by most recent
  • Get games with the most open tickets
  • Get ticket statistics for a specific user by username
  • Get ticket statistics for a specific game by game ID
  • Get ticket statistics for a specific achievement by achievement ID

This should be done in a way that isn't a breaking change, so maybe detect the legacy query params and fall through to the new endpoint code. Ideally, API_GetTicketData's primary job is to satisfy the "get details for a specific ticket" use case.

@wescopeland wescopeland added kind/enhancement New feature or request area/api-web Web API labels Feb 25, 2024
@wescopeland wescopeland self-assigned this Feb 25, 2024
@wescopeland wescopeland removed their assignment Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api-web Web API kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant