Closed theycallmeswift closed 3 months ago
[!WARNING]
Rate limit exceeded
@theycallmeswift has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 4 minutes and 33 seconds before requesting another review.
How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. 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](https://coderabbit.ai/docs/faq) for further information.Commits
Files that changed from the base of the PR and between 4d1788ca2bef5dbe7ed21f53cc009d0afc0ad875 and 254773c0a8d6c394d766f242dce04d88fa6027f3.
The recent updates introduce significant enhancements to the CI workflow, formatting rules for YAML files, and the FlatfileClient
API. A new testing step has been added to the CI process to ensure that tests are executed immediately after building, improving code quality. Additionally, the visibility of internal interfaces in the FlatfileClient
has been enhanced by exporting them, and the test suite for FlatfileClient
has been restructured to ensure effective coverage.
File | Change Summary |
---|---|
.github/workflows/ci.yml |
Added a "Run tests" job to execute yarn run test after the "Compile" job, enhancing CI processes. |
.prettierrc.yml |
Introduced overrides to set tabWidth: 2 for *.yml files, while maintaining the default tabWidth: 4 for others. |
src/Client.ts |
Exported Options and RequestOptions interfaces in the FlatfileClient namespace for better modularity. |
tests/client.test.ts |
Replaced previous content with a focused test suite to verify instantiation of FlatfileClient . |
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
This is actually a non-issue. Closing!
Currently we have a conflict between the
FlatfileClient
type namespace and the class itself. If you try to instantiate aFlatfileClient
object, you will get the following error:I've also added a Jest test that will fail if this regresses in the future.