-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(rfq-indexer): add missing fields #3309
Conversation
Note Currently processing new changes in this PR. This may take a few minutes, please wait... 📒 Files selected for processing (3)
WalkthroughThe pull request introduces modifications to the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
Deploying sanguine-fe with Cloudflare Pages
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## feat/explorer-w #3309 +/- ##
===================================================
Coverage 90.44834% 90.44834%
===================================================
Files 54 54
Lines 1026 1026
Branches 82 82
===================================================
Hits 928 928
Misses 95 95
Partials 3 3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
* explorer UI updated * rfq-indexer update * explorer backend update * [goreleaser] trigger explorer version bump * rfq indexer with the right contracts * [goreleaser] adding catch * response error fixes and wld decimals * adding address * feat(rfq-indexer): add `request` column to `BridgeRequested` for refunds (#3287) * feat(rfq-relayer): add MaxRelayAmount (#3259) * Feat: add quoteParams helper for test * Feat: add MaxQuoteAmount to relconfig * Feat: use MaxQuoteAmount * Feat: handle MaxQuoteAmount in quoter test * Replace: MaxQuoteAmount -> MaxRelayAmount * Feat: shouldProcess() returns false if max relay amount exceeded * Feat: add test for MaxRelayAmount * add request field for refunds * adding to events typing --------- Co-authored-by: dwasse <wassermandaniel8@gmail.com> Co-authored-by: defi-moses <jakedinero@protonmail.com> * fix api docs * linting fixes * fixing irrelavent files * wc fixes and tests solved * fix linting errors * [goreleaser] * refining tests * adding bridge Module to graphql * Adding to all bridge watcher queries * adding worldchain to the chart * adding other rfq events to the rfq events db * fixing wld coingecko ticker [goreleaser] * [goreleaser] coingecko update and new topic parsing * small lint fix * [goreleaser] linting fixes * fix(rfq-indexer): add missing fields (#3309) * add missing fields --------- Co-authored-by: abtestingalpha <abtestingalpha@gmail.com> --------- Co-authored-by: vro <168573323+golangisfun123@users.noreply.github.com> Co-authored-by: dwasse <wassermandaniel8@gmail.com> Co-authored-by: abtestingalpha <abtestingalpha@gmail.com>
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
originChainId
andoriginChain
properties.originChainId
and amounts.These changes contribute to more effective processing of bridge proof disputes and enhance the clarity and consistency of data handling across bridge events.