Closed AJAYK-01 closed 11 months ago
[!WARNING]
Rate Limit Exceeded
@AJAYK-01 has exceeded the limit for the number of files or commits that can be reviewed per hour. Please wait 4 minutes and 42 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. 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 e51bed6b99699386a05a790a0c594fd2ce86076f and b7e74d1ceb6a6c7745e6cc1cbe2115f3f50a19be.
The changes involve the introduction of a new feature in a browser extension that checks the login status of a user on GitHub and Bitbucket. When the user is not logged in, a visual indicator is added to the interface. This is achieved through new functions for checking login status, message handling in the background script, and UI updates in the orchestrator script. The utilities are updated to create and destroy new UI elements, and the main CSS is updated to style the new indicator.
File Path | Change Summary |
---|---|
backgroundScript.js | Added checkLoginStatus function and message listener for login status checks, with error handling. |
scripts/orchestrator.js | Updated to call addSignedOutIndicator for GitHub and Bitbucket URLs, with minor conditional and formatting changes. |
scripts/signedOutIndicator.js | Introduced addSignedOutIndicator function to send messages and handle responses for login status. |
scripts/utilities.js | Modified createElement and destroyElement functions to support new "github", "bitbucket", and "login" UI elements. |
scripts/main.css | Added styles for #vibinex-indicator and its child img , and removed a comment block. |
e0c8b25 adds the enhancement over the initial commits to check for the correct auth provider which is logged in. For eg, if user is logged in to Vibinex via Github but is currently on a Bitbucket repo page, then the indicator will still be present due to this check.
However, whilst working on this enhancement, I found that the backend api has a bug, which returns multiple logged in auth tokens if I had previously logged into another provider. For eg, consider the below condition:
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell
No Coverage information
0.0% Duplication
What this PR is about:
Summary by CodeRabbit
New Features
Enhancements
Bug Fixes
Style
Chores