Conversation
Add GET /gaming/games/by-slug/{slug}, returning the same payload as the
id route and 404ing inactive or unplayable games.
okapitula
requested review from
damianrzepka,
jakubfilinger-b,
klaudia-blazyczek-blurify,
marek-chmielowski-blurify,
mp-blurify and
zaxovaiko
as code owners
September 25, 2026 12:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
GET /gaming/games/by-slug/{slug}, a public lookup that returns the sameGameSchemapayload asGET /gaming/games/{id}.Why
A game detail page is addressed by its slug, not its UUID. Before this, a frontend had to list games and filter them client-side to resolve a slug. The new route applies the same playability filter as the id route: an inactive or unplayable game returns 404, and a malformed slug returns 400.
Alternatives considered
slugfilter on the list route. Rejected: the list route is paginated and returns an array, so a detail page would have to unwrap it and handle an empty page itself.Risks
None. This is an additive route.
getGamenow shares its lookup logic withgetGameBySlugthrough a privatefindGame, and its behaviour is unchanged.