Skip to content
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

refactor(rfq): move chain utils to new util pkg #2982

Merged
merged 5 commits into from
Aug 6, 2024
Merged

Conversation

dwasse
Copy link
Collaborator

@dwasse dwasse commented Aug 6, 2024

Summary by CodeRabbit

  • Bug Fixes
    • Updated the source of the Ethereum address in various functions to improve clarity and maintainability.
  • New Features
    • Introduced a new utility package enhancing the organization of Ethereum address utilities.
  • Documentation
    • Added package-level documentation for the new utility package, clarifying its purpose and usage.
  • Chores
    • Simplified GitHub Actions workflow conditions for better readability and maintainability.

@github-actions github-actions bot added go Pull requests that update Go code size/s labels Aug 6, 2024
Copy link
Contributor

coderabbitai bot commented Aug 6, 2024

Walkthrough

The changes primarily involve refactoring the source of Ethereum address constants from the chain package to the util package across various files in the RFQ service. This update enhances code clarity and maintainability by consolidating the address source, although it does not introduce new functionality. Imports and logic have been adjusted accordingly, marking a shift in how utilities are organized and accessed.

Changes

Files & Paths Change Summary
services/rfq/e2e/rfq_test.go, setup_test.go, relayer/chain/chain.go, relayer/inventory/manager.go, relayer/quoter/quoter.go, relayer/quoter/quoter_test.go, relayer/quoter/suite_test.go, relayer/relapi/client_test.go, relayer/relapi/handler.go, relayer/relapi/suite_test.go, relayer/relconfig/config.go, relayer/service/chainindexer.go, relayer/service/statushandler.go Replaced references to chain.EthAddress with util.EthAddress across multiple functions and tests, improving maintainability and clarity. New imports for util were introduced where necessary.
services/rfq/util/doc.go, util/util.go Introduced a new doc.go for documentation in the util package and changed util.go's package declaration from chain to util, indicating a reorganization.
.github/workflows/go.yml Adjusted GitHub Actions workflow conditions, simplifying job triggers and improving YAML readability without changing core functionality.

Sequence Diagram(s)

sequenceDiagram
    participant TestSuite
    participant Util

    TestSuite->>Util: Request EthAddress
    Util-->>TestSuite: Provide EthAddress
    TestSuite->>Util: Check IsGasToken
    Util-->>TestSuite: GasToken Validation Result
Loading

Poem

🐇 In the code where bunnies hop,
Ethereum's address took a swap.
From chain to util, clear and bright,
Refactoring brings a joyful light!
So here’s to change, so swift and neat,
A codebase fresh, a tasty treat! 🥕


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?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

cloudflare-workers-and-pages bot commented Aug 6, 2024

Deploying sanguine-fe with  Cloudflare Pages  Cloudflare Pages

Latest commit: 13319d5
Status: ✅  Deploy successful!
Preview URL: https://8fbe4c16.sanguine-fe.pages.dev
Branch Preview URL: https://feat-rfq-util.sanguine-fe.pages.dev

View logs

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between fad41f8 and 0d6e4e6.

Files selected for processing (15)
  • services/rfq/e2e/rfq_test.go (4 hunks)
  • services/rfq/e2e/setup_test.go (4 hunks)
  • services/rfq/relayer/chain/chain.go (2 hunks)
  • services/rfq/relayer/inventory/manager.go (7 hunks)
  • services/rfq/relayer/quoter/quoter.go (2 hunks)
  • services/rfq/relayer/quoter/quoter_test.go (6 hunks)
  • services/rfq/relayer/quoter/suite_test.go (3 hunks)
  • services/rfq/relayer/relapi/client_test.go (3 hunks)
  • services/rfq/relayer/relapi/handler.go (2 hunks)
  • services/rfq/relayer/relapi/suite_test.go (2 hunks)
  • services/rfq/relayer/relconfig/config.go (2 hunks)
  • services/rfq/relayer/service/chainindexer.go (2 hunks)
  • services/rfq/relayer/service/statushandler.go (2 hunks)
  • services/rfq/util/doc.go (1 hunks)
  • services/rfq/util/util.go (1 hunks)
Files skipped from review due to trivial changes (2)
  • services/rfq/util/doc.go
  • services/rfq/util/util.go
Additional context used
Learnings (2)
services/rfq/relayer/relapi/client_test.go (1)
Learnt from: trajan0x
PR: synapsecns/sanguine#2815
File: services/rfq/relayer/relapi/handler.go:162-165
Timestamp: 2024-07-02T14:49:46.636Z
Learning: When adding new validation logic in the `Withdraw` function, ensure to export helper functions like `toAddressIsWhitelisted` for direct unit testing.
services/rfq/relayer/relapi/handler.go (1)
Learnt from: trajan0x
PR: synapsecns/sanguine#2815
File: services/rfq/relayer/relapi/handler.go:162-165
Timestamp: 2024-07-02T14:49:46.636Z
Learning: When adding new validation logic in the `Withdraw` function, ensure to export helper functions like `toAddressIsWhitelisted` for direct unit testing.
Additional comments not posted (26)
services/rfq/relayer/chain/chain.go (2)

19-19: LGTM!

The addition of the util import aligns with the refactoring objectives.


79-81: LGTM! But verify the function usage in the codebase.

The change enhances modularity and maintainability by centralizing the logic for determining gas tokens within the util package.

However, ensure that all function calls to IsGasToken are correctly updated to reference util.IsGasToken.

Verification successful

Verification successful!

All function calls to IsGasToken are correctly updated to reference util.IsGasToken. The remaining instances are part of struct fields or variable names and do not require changes.

  • services/rfq/relayer/relapi/handler.go
  • services/rfq/relayer/quoter/quoter.go
  • services/rfq/relayer/chain/chain.go
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all function calls to `IsGasToken` reference `util.IsGasToken`.

# Test: Search for the function usage. Expect: Only occurrences of `util.IsGasToken`.
rg --type go -A 5 $'IsGasToken'

Length of output: 3921

services/rfq/relayer/quoter/suite_test.go (2)

19-19: LGTM!

The import statement change aligns with the refactoring objectives and centralizes the utility functions.


56-56: LGTM! But verify the function usage in the codebase.

The change aligns with the refactoring objectives and centralizes the utility functions.

However, ensure that all references to EthAddress.String() are correctly updated to reference util.EthAddress.String().

Also applies to: 81-81

Verification successful

All references to EthAddress.String() have been correctly updated to util.EthAddress.String().

The refactoring aligns with the objectives and centralizes the utility functions.

  • services/rfq/relayer/quoter/suite_test.go
  • services/rfq/relayer/quoter/quoter_test.go
  • services/rfq/relayer/relconfig/config.go
  • services/rfq/e2e/setup_test.go
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all references to `EthAddress.String()` reference `util.EthAddress.String()`.

# Test: Search for the function usage. Expect: Only occurrences of `util.EthAddress.String()`.
rg --type go -A 5 $'EthAddress.String()'

Length of output: 3238

services/rfq/relayer/service/chainindexer.go (2)

17-17: LGTM!

The import statement change aligns with the refactoring objectives and centralizes the utility functions.


183-183: LGTM! But verify the function usage in the codebase.

The change aligns with the refactoring objectives and centralizes the utility functions.

However, ensure that all references to EthAddress are correctly updated to reference util.EthAddress.

Verification successful

All references to EthAddress have been correctly updated to util.EthAddress.

The search results confirm that the change aligns with the refactoring objectives, and the references are consistent across the codebase.

  • services/rfq/util/util.go
  • services/rfq/e2e/setup_test.go
  • services/rfq/relayer/service/statushandler.go
  • services/rfq/relayer/quoter/suite_test.go
  • services/rfq/relayer/quoter/quoter_test.go
  • services/rfq/relayer/relapi/client_test.go
  • services/rfq/e2e/rfq_test.go
  • services/rfq/relayer/relconfig/config.go
  • services/rfq/relayer/service/chainindexer.go
  • services/rfq/relayer/relapi/suite_test.go
  • services/rfq/relayer/inventory/manager.go
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all references to `EthAddress` reference `util.EthAddress`.

# Test: Search for the function usage. Expect: Only occurrences of `util.EthAddress`.
rg --type go -A 5 $'EthAddress'

Length of output: 13068

services/rfq/relayer/relapi/client_test.go (2)

75-75: LGTM!

The reference to chain.EthAddress has been correctly updated to util.EthAddress.


174-174: LGTM!

The reference to chain.EthAddress has been correctly updated to util.EthAddress.

services/rfq/relayer/relapi/suite_test.go (2)

107-107: LGTM!

The reference to chain.EthAddress has been correctly updated to util.EthAddress in the QuotableTokens map.


110-110: LGTM!

The reference to chain.EthAddress has been correctly updated to util.EthAddress in the QuotableTokens map.

services/rfq/relayer/service/statushandler.go (2)

19-19: LGTM!

The import for util has been correctly added to the file.


179-179: LGTM!

The reference to chain.EthAddress has been correctly updated to util.EthAddress in the gasMiddleware function.

services/rfq/relayer/relapi/handler.go (1)

220-220: Verify the usage of util.IsGasToken.

Ensure that the util.IsGasToken function behaves as expected and is correctly integrated. This change centralizes the gas token identification logic, which is a good practice.

Verification successful

Verify the definition and usage of EthAddress.

Ensure that EthAddress is correctly defined and used within the util package to ensure the IsGasToken function behaves as expected.


The usage of util.IsGasToken is verified and correct.

The util.IsGasToken function and EthAddress are correctly implemented and consistently used across the codebase. The change centralizes the gas token identification logic, which is a good practice.

  • util.IsGasToken is correctly defined in services/rfq/util/util.go.
  • EthAddress is correctly defined and used throughout the project.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the implementation of `util.IsGasToken` function.

# Test: Search for the function definition. Expect: Correct implementation.
rg --type go -A 5 $'func IsGasToken'

Length of output: 190


Script:

#!/bin/bash
# Description: Verify the definition and usage of `EthAddress`.

# Test: Search for the definition of `EthAddress`. Expect: Correct definition.
rg --type go -A 5 $'EthAddress'

Length of output: 13068

services/rfq/relayer/quoter/quoter_test.go (1)

46-46: Verify the usage of util.EthAddress.

Ensure that the util.EthAddress constant is correctly integrated and behaves as expected. This change centralizes the Ethereum address reference, which is a good practice.

Also applies to: 57-57, 59-59, 71-71, 82-82, 84-84, 96-96

Verification successful

The util.EthAddress constant is correctly defined and integrated.

The change centralizes the Ethereum address reference, which is a good practice and ensures consistency across the codebase.

  • util.EthAddress is defined as common.HexToAddress("0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE") in services/rfq/util/util.go.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the definition of `util.EthAddress` constant.

# Test: Search for the constant definition. Expect: Correct implementation.
rg --type go -A 5 $'var EthAddress'

Length of output: 415

services/rfq/relayer/relconfig/config.go (1)

262-262: Verify the usage of util.EthAddress.String().

Ensure that the util.EthAddress.String() constant is correctly integrated and behaves as expected. This change centralizes the Ethereum address reference, which is a good practice.

Verification successful

Verified the usage of util.EthAddress.String().

The util.EthAddress is defined using common.HexToAddress, which returns an Ethereum address type from the go-ethereum library. This type inherently has a String method. The change centralizes the Ethereum address reference correctly.

  • services/rfq/util/util.go: var EthAddress = common.HexToAddress("0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE")
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the definition of `util.EthAddress` constant and its `String` method.

# Test: Search for the constant definition and usage of the `String` method. Expect: Correct implementation.
rg --type go -A 5 $'var EthAddress'

Length of output: 415


Script:

#!/bin/bash
# Description: Verify the implementation and usage of the String method for EthAddress.

# Test: Search for the String method implementation related to EthAddress. Expect: Correct implementation and usage.
rg --type go 'EthAddress.String()'

Length of output: 800


Script:

#!/bin/bash
# Description: Verify the implementation of the String method for EthAddress.

# Test: Search for the String method implementation in the codebase. Expect: Correct implementation.
rg --type go 'func (e EthAddress) String()'

Length of output: 45


Script:

#!/bin/bash
# Description: Verify the definition of common.HexToAddress and the type it returns.

# Test: Search for the definition of HexToAddress in the common package. Expect: Identification of the type returned.
rg --type go 'func HexToAddress' -A 5

Length of output: 39


Script:

#!/bin/bash
# Description: Verify the definition of common.HexToAddress and the type it returns.

# Test: Search for the definition of HexToAddress in the common package with a broader search pattern. Expect: Identification of the type returned.
rg --type go 'HexToAddress'

Length of output: 35644

services/rfq/e2e/setup_test.go (4)

244-246: LGTM!

The change from chain.EthAddress to util.EthAddress is consistent and correct.


257-259: LGTM!

The change from chain.EthAddress to util.EthAddress is consistent and correct.


382-384: LGTM!

The change from chain.EthAddress to util.EthAddress is consistent and correct.


385-387: LGTM!

The change from chain.EthAddress to util.EthAddress is consistent and correct.

services/rfq/e2e/rfq_test.go (3)

291-293: LGTM!

The change from chain.EthAddress to util.EthAddress is consistent and correct.


311-313: LGTM!

The change from chain.EthAddress to util.EthAddress is consistent and correct.


356-358: LGTM!

The change from chain.EthAddress to util.EthAddress is consistent and correct.

services/rfq/relayer/quoter/quoter.go (1)

542-544: LGTM!

The change from chain.IsGasToken to util.IsGasToken is consistent and correct.

services/rfq/relayer/inventory/manager.go (3)

Line range hint 98-103:
LGTM! But verify the function usage in the codebase.

The code changes are approved.

However, ensure that all function calls to GetCommittableBalance match the new reference to util.EthAddress.

Verification successful

Verification successful: All function calls to GetCommittableBalance match the new reference to util.EthAddress.

The changes are consistent across the codebase.

  • services/rfq/relayer/service/statushandler.go
  • services/rfq/relayer/service/handlers.go
  • services/rfq/relayer/quoter/quoter.go
  • services/rfq/relayer/inventory/manager.go
  • services/rfq/relayer/inventory/mocks/manager.go
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all function calls to `GetCommittableBalance` match the new reference to `util.EthAddress`.

# Test: Search for the function usage. Expect: Only occurrences of the new reference.
rg --type go -A 5 $'GetCommittableBalance'

Length of output: 7134


544-546: LGTM! But verify the function usage in the codebase.

The code changes are approved.

However, ensure that all function calls to initializeTokens match the new reference to util.EthAddress.

Verification successful

Verified: The function usage matches the new reference to util.EthAddress.

The references to util.EthAddress are correctly used within the file services/rfq/relayer/inventory/manager.go.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all function calls to `initializeTokens` match the new reference to `util.EthAddress`.

# Test: Search for the function usage. Expect: Only occurrences of the new reference.
rg --type go -A 5 $'initializeTokens'

Length of output: 1513


Script:

#!/bin/bash
# Description: Verify the reference to `util.EthAddress` in the file `services/rfq/relayer/inventory/manager.go`.

# Test: Search for the reference to `util.EthAddress` in the file.
rg --type go 'util.EthAddress' services/rfq/relayer/inventory/manager.go

Length of output: 519


Line range hint 314-352:
LGTM! But verify the function usage in the codebase.

The code changes are approved.

However, ensure that all function calls to ApproveAllTokens match the new reference to util.EthAddress.

Verification successful

All instances of util.EthAddress are correctly referenced within the ApproveAllTokens method.

The verification confirms that the method ApproveAllTokens in services/rfq/relayer/inventory/manager.go correctly uses util.EthAddress in all necessary places.

  • services/rfq/relayer/inventory/manager.go
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all function calls to `ApproveAllTokens` match the new reference to `util.EthAddress`.

# Test: Search for the function usage. Expect: Only occurrences of the new reference.
rg --type go -A 5 $'ApproveAllTokens'

Length of output: 2465


Script:

#!/bin/bash
# Description: Verify the usage of `util.EthAddress` within the `ApproveAllTokens` method.

# Test: Search for `util.EthAddress` within the method definition.
rg --type go -A 10 'func (i *inventoryManagerImpl) ApproveAllTokens(ctx context.Context) error' | rg 'util\.EthAddress'

Length of output: 121


Script:

#!/bin/bash
# Description: Verify the usage of `util.EthAddress` within the `ApproveAllTokens` method.

# Test: Search for `util.EthAddress` within the entire method definition.
rg --type go -A 50 'func (i *inventoryManagerImpl) ApproveAllTokens(ctx context.Context) error' services/rfq/relayer/inventory/manager.go | rg 'util\.EthAddress'

Length of output: 163


Script:

#!/bin/bash
# Description: Verify the usage of `util.EthAddress` within the entire `services/rfq/relayer/inventory/manager.go` file.

# Test: Search for `util.EthAddress` within the entire file.
rg 'util\.EthAddress' services/rfq/relayer/inventory/manager.go

Length of output: 512

Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

This pull request refactors the RFQ (Request for Quote) service by moving chain utilities from the 'chain' package to a new 'util' package, improving code organization and potential reusability.

  • Created new services/rfq/util package with EthAddress and IsGasToken functions
  • Updated import statements across multiple files to use the new util package
  • Replaced chain.EthAddress and chain.IsGasToken references with util.EthAddress and util.IsGasToken
  • Removed IsGasToken function from services/rfq/relayer/chain/chain.go
  • Added services/rfq/util/doc.go to describe the purpose of the new utility package

15 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings

@github-actions github-actions bot added the M-ci Module: CI label Aug 6, 2024
Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

(updates since last review)

No major changes found since last review. The previous summary accurately captures the key points of the refactoring, and there are no significant new changes to report.

No file(s) reviewed, no comment(s)
Edit PR Review Bot Settings

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0d6e4e6 and 8b3bbab.

Files selected for processing (1)
  • .github/workflows/go.yml (6 hunks)
Additional comments not posted (4)
.github/workflows/go.yml (4)

7-8: Verify exclusion of fe-release branch.

Ensure that excluding the fe-release branch from the workflow is intentional and aligns with the overall workflow strategy.


80-81: LGTM! Verify the correctness of updated conditions.

The changes simplify the runs-on condition and refine the if condition, enhancing readability and maintainability.

Ensure that the updated conditions work as expected.


112-112: Verify exclusion of runners containing 'nsc' from caching.

Ensure that excluding runners with names containing 'nsc' from caching is intentional and aligns with the overall caching strategy.


234-234: LGTM! Cleanup approved.

Removing the commented-out if condition cleans up the configuration file without impacting functionality.

Copy link

codecov bot commented Aug 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 25.71691%. Comparing base (e84f0f6) to head (13319d5).
Report is 24 commits behind head on master.

Additional details and impacted files
@@                 Coverage Diff                 @@
##              master       #2982         +/-   ##
===================================================
+ Coverage   25.70802%   25.71691%   +0.00888%     
===================================================
  Files            771         771                 
  Lines          55613       55551         -62     
  Branches          80          82          +2     
===================================================
- Hits           14297       14286         -11     
+ Misses         39830       39781         -49     
+ Partials        1486        1484          -2     
Flag Coverage Δ
opbot 0.48900% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

(updates since last review)

This PR introduces improvements to the token approval process in the RFQ (Request for Quote) system's end-to-end tests, focusing on error handling and retry logic.

  • Enhanced Approve function in services/rfq/e2e/setup_test.go with retry mechanism using retry.WithBackoff
  • Added context and time imports to support the new retry logic
  • Improved error handling with detailed error messages in the Approve function
  • Introduced a 15-second maximum retry time for token approvals
  • Utilized core.CopyBigInt for safer big integer operations in the approval process

These changes significantly improve the reliability and robustness of the e2e test setup for the RFQ system.

1 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings

Comment on lines +216 to +218
if err != nil {
return fmt.Errorf("could not get token at %s: %w", token.Address().String(), err)
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

style: Ensure error messages are consistent with project standards

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8b3bbab and 13319d5.

Files selected for processing (1)
  • services/rfq/e2e/setup_test.go (7 hunks)
Files skipped from review as they are similar to previous changes (1)
  • services/rfq/e2e/setup_test.go

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go Pull requests that update Go code M-ci Module: CI size/s
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant