Open Mati365 opened 3 weeks ago
[!WARNING]
Rate Limit Exceeded
@godai78 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 52 minutes and 39 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 8ef7c4cfcdb62485b2d66fdc03d6cd9cdf5ae6bb and 2e940125945681769d552dfd4de8b20cd88c660d.
The recent update enhances the CKEditorContext
component in React by introducing the onAfterDestroy
property. This new feature improves lifecycle management by executing a callback after successfully destroying an editor instance, aiding in error recovery and reinitialization scenarios.
File Path | Change Summary |
---|---|
docs/installation/integrations/react.md |
Added onAfterDestroy property to CKEditorContext in React, invoked post-editor destruction, including after reinitialization in error scenarios. Note: Callback may occur when component is unmounted. |
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?
Suggested merge commit message (convention)
Docs: Add
onAfterDestroy
callback description to react integration docs.Summary by CodeRabbit
onAfterDestroy
callback in theCKEditorContext
component.