Closed golangisfun123 closed 1 week ago
[!WARNING]
Rate limit exceeded
@golangisfun123 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 2 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 1ac6a130aeecbfc6ef2f2c76bcba84aeaee89f42 and 7c700a9613126dfc7de823cb034595aa094ba4ac.
This update introduces a consistent data structure for handling blacklisted addresses across various components of the screener-api. A new Data
struct is added to encapsulate address-related information, leading to changes in struct definitions, initializations, and JSON handling. Additionally, a new setting for font ligatures has been added to the .vscode settings.
Files | Change Summary |
---|---|
.vscode/settings.json |
Added font ligature settings for the VS Code editor. |
client/client.go |
Modified BlackListBody struct to include a nested Data struct with Address , Network , and Tag . |
db/db_test.go |
Refactored test cases to accommodate the new Data struct in BlacklistedAddress . |
db/models.go |
Restructured BlacklistedAddress struct to embed the new Data struct. |
screener/screener.go |
Updated blacklistAddress method to utilize the nested Data struct for blacklist handling. |
screener/suite_test.go |
Refactored blacklistTestWithOperation function to initialize BlackListBody with the nested Data struct and removed unnecessary JSON marshaling. |
In the realm of code so bright, Structures changed, new fields in sight. With a nested
Data
tree, Cleaner code for all to see. Font ligatures in VS Code too, Bringing elegance to the view. Cheers to progress, hop along, In the world where code belongs! 🐇✨
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?
Latest commit: |
7c700a9
|
Status: | ✅ Deploy successful! |
Preview URL: | https://4c1b11f0.sanguine-fe.pages.dev |
Branch Preview URL: | https://fix-data.sanguine-fe.pages.dev |
Attention: Patch coverage is 70.58824%
with 5 lines
in your changes missing coverage. Please review.
Project coverage is 25.73669%. Comparing base (
08e2b19
) to head (7c700a9
). Report is 9 commits behind head on master.
Files | Patch % | Lines |
---|---|---|
contrib/screener-api/db/sql/base/namer.go | 0.00000% | 4 Missing :warning: |
contrib/screener-api/db/sql/base/base.go | 0.00000% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Description A clear and concise description of the features you're adding in this pull request.
Additional context Add any other context about the problem you're solving.
Metadata
Summary by CodeRabbit
New Features
Refactor
BlackListBody
andBlacklistedAddress
data models to utilize a nestedData
struct.Bug Fixes
BlackListBody
in various functions and tests for better data management and readability.