Skip to content

fix(contract): add /catalog/books/{id}/availability to vendored OpenAPI#3

Closed
fabiodalez-dev wants to merge 1 commit into
mainfrom
fix/openapi-contract-availability
Closed

fix(contract): add /catalog/books/{id}/availability to vendored OpenAPI#3
fabiodalez-dev wants to merge 1 commit into
mainfrom
fix/openapi-contract-availability

Conversation

@fabiodalez-dev

Copy link
Copy Markdown
Owner

P3 from the mobile review. The backend exposes GET /catalog/books/{id}/availability and Retrofit (PinakesApi) already calls it, but the vendored _contract/openapi.json was missing that path (jumped from /catalog/books/{id} to /catalog/genres — 24 vs the backend's 25 paths). Synced the contract (now 25 paths, exactly matching the backend). Documentation only — no runtime change.

…ed OpenAPI

The backend exposes GET /catalog/books/{id}/availability (and Retrofit already
calls it), but the vendored _contract/openapi.json jumped from /catalog/books/{id}
straight to /catalog/genres. Sync the contract (25 paths, matching the backend)
so the reference doc reflects what the client actually uses. No runtime change.
@coderabbitai

coderabbitai Bot commented Jun 24, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@fabiodalez-dev, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 17 minutes and 18 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a6d6fa9e-b0c1-4f80-aa22-c9adf40473ac

📥 Commits

Reviewing files that changed from the base of the PR and between 845ae1f and 25cb257.

📒 Files selected for processing (1)
  • _contract/openapi.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/openapi-contract-availability

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@fabiodalez-dev

Copy link
Copy Markdown
Owner Author

Superseded by #5 (consolidated Mobile API contract alignment). Changes included there.

@fabiodalez-dev fabiodalez-dev deleted the fix/openapi-contract-availability branch June 25, 2026 06:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant