Repository navigation
feat(api): add personalized to the related movie and show routes - #1055
Merged
Merged
Conversation
vladjerca
marked this pull request as ready for review
November 2, 2026 19:03
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Adds an optional
personalizedboolean toGET /movies/:id/relatedandGET /shows/:id/related.When it is
trueand the caller is a VIP or director, the API returns the same related titles re-ordered toward the caller's taste. For everyone else the param is ignored and the list is unchanged.personalizedQuerySchema, merged into both related routes.The server change that reads the param is in review and not live yet. Clients should not send it until it is, and the SDK publish waits for that too. Until then the API ignores the param.
The
/related/smartaliases are not modeled in the SDK, so they have nothing to change here.Test plan
bun run checkandbun testinprojects/apibun run publish:checkbun run openapi:validate