fix: public API continous screening schema#1702
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 52 minutes and 54 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdated the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
dc67105 to
62abbc0
Compare
Pascal-Delange
left a comment
There was a problem hiding this comment.
Actually, I'm not sure about this.
I know the current implementation technically allows it, but I wasn't quite sure if that's what we want to commit on, mostly because it makes for different indexing performance.
I just don't know on the top of my head TBH so let's discuss this one again after the release
This pull request updates the OpenAPI schema in
pubapi/openapi/v1beta.ymlto correctly specify that certain query parameters accept arrays of UUID strings, improving the accuracy of the API documentation and client generation.OpenAPI schema improvements:
schemafor relevant query parameters to explicitly declare them as arrays of strings with UUID format in four different endpoints. This clarifies that these parameters can accept multiple values and ensures better compatibility with OpenAPI tools. [1] [2] [3] [4]Summary by CodeRabbit