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

feat: create deploySingleRequestProxy functionality in the sdk #1474

Merged

Conversation

aimensahnoun
Copy link
Member

@aimensahnoun aimensahnoun commented Oct 22, 2024

Description of the changes

resolve #1396

  • Add deploySingleRequestProxy function in payment-processor to deploy Single Request Proxy for a request.
  • Add payRequestWithSingleRequestProxy function in payment-processor to easily make payments through a Single Request Proxy.

Summary by CodeRabbit

Release Notes

  • New Features

    • Introduced a Single Request Proxy functionality for managing payments on Ethereum, allowing for more flexible payment processing.
    • Added fee handling capabilities in payment requests, enhancing the detail and control over payment transactions.
    • Expanded the public API to include the SingleRequestProxyFactory, facilitating easier access to new payment functionalities.
    • Enhanced module export capabilities with additional functionalities for single request processing.
  • Bug Fixes

    • Improved error handling in payment processing functions to ensure reliability and robustness.
  • Tests

    • Added comprehensive unit tests for the new Single Request Proxy features, ensuring functionality and error management are thoroughly validated.

Copy link
Contributor

coderabbitai bot commented Oct 25, 2024

Walkthrough

The changes in this pull request introduce a new module for managing Single Request Proxy contracts within the payment-processor package. Key additions include the implementation of multiple asynchronous functions for deploying and processing payments through Single Request Proxy contracts, alongside comprehensive unit tests for these functionalities. The export capabilities of the payment-processor module are enhanced to include the new proxy functionalities. Additionally, updates to the RequestNetwork class improve payment request handling by incorporating fee information.

Changes

File Change Summary
packages/payment-processor/src/index.ts Added export statement for single-request-proxy.
packages/payment-processor/src/payment/single-request-proxy.ts Introduced multiple async functions: deploySingleRequestProxy, validateSingleRequestProxy, payWithERC20SingleRequestProxy, payWithEthereumSingleRequestProxy, and payRequestWithSingleRequestProxy.
packages/payment-processor/test/payment/single-request-proxy.test.ts Created unit tests for the new functions, covering various payment scenarios and error handling.
packages/request-client.js/src/api/request-network.ts Modified prepareRequestDataForPayment to include feeAddress and feeAmount.
packages/smart-contracts/scripts/test-deploy-all.ts Added import and call to deploySingleRequestProxyFactory in the deployment sequence.
packages/smart-contracts/scripts/test-deploy-single-request-proxy.ts Introduced deploySingleRequestProxyFactory function for deploying the SingleRequestProxyFactory contract.
packages/smart-contracts/src/lib/artifacts/SingleRequestProxyFactory/0.1.0.json Added ABI definition for SingleRequestProxyFactory with relevant functions and events.
packages/smart-contracts/src/lib/artifacts/SingleRequestProxyFactory/index.ts Created index file exporting singleRequestProxyFactoryArtifact.
packages/smart-contracts/src/lib/artifacts/index.ts Added export statement for SingleRequestProxyFactory.
packages/smart-contracts/src/contracts/SingleRequestProxyFactory.sol Updated event signatures for EthereumSingleRequestProxyCreated and ERC20SingleRequestProxyCreated.

Assessment against linked issues

Objective Addressed Explanation
Support SingleRequestProxy in payment-processor package (#[1396])

Possibly related PRs

Suggested reviewers

  • yomarion
  • kevindavee
  • MantisClone
  • sstefdev
  • alexandre-abrioux

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between 47afd3b and 958ebf1.

📒 Files selected for processing (1)
  • packages/payment-processor/src/payment/single-request-proxy.ts (1 hunks)
🧰 Additional context used
📓 Learnings (1)
packages/payment-processor/src/payment/single-request-proxy.ts (3)
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1474
File: packages/payment-processor/src/payment/single-request-proxy.ts:156-160
Timestamp: 2024-10-28T15:52:05.032Z
Learning: When determining if a `SingleRequestProxy` is an `ERC20SingleRequestProxy` or an `EthereumSingleRequestProxy`, include a comment explaining that the presence of `tokenAddress` distinguishes between the two.
Learnt from: aimensahnoun
PR: RequestNetwork/requestNetwork#1474
File: packages/payment-processor/src/payment/single-request-proxy.ts:202-209
Timestamp: 2024-10-29T09:00:54.169Z
Learning: In the `packages/payment-processor/src/payment/single-request-proxy.ts` file, within the `payWithEthereumSingleRequestProxy` function, the current error handling is acceptable as per the project's expectations.
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1474
File: packages/payment-processor/src/payment/single-request-proxy.ts:156-160
Timestamp: 2024-10-28T15:52:05.032Z
Learning: In the `payRequestWithSingleRequestProxy` function of `single-request-proxy.ts`, failing to retrieve `tokenAddress()` is expected for `EthereumSingleRequestProxy` contracts and is not an error.
🔇 Additional comments (5)
packages/payment-processor/src/payment/single-request-proxy.ts (5)

24-107: Function deploySingleRequestProxy is well-implemented

The function correctly handles the deployment of Single Request Proxy contracts, including validation of payment networks, error handling, and transaction management.


115-135: Function validateSingleRequestProxy performs necessary contract validation

The validation logic ensures that the proxy contract has the required methods, enhancing the reliability of the system.


144-179: Function payWithERC20SingleRequestProxy correctly processes ERC20 payments

The function handles ERC20 token transfers and triggers the proxy's receive function appropriately.


188-222: Function payWithEthereumSingleRequestProxy correctly processes Ethereum payments

The function handles ETH transfers to the proxy contract, ensuring proper execution of Ethereum payments.


240-271: Function payRequestWithSingleRequestProxy accurately delegates to appropriate payment functions

The function determines the proxy type and calls the correct payment function, enhancing usability and maintaining code modularity.


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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

@aimensahnoun aimensahnoun force-pushed the 1396-support-singlerequestproxy-in-the-request-network-sdk branch from 45cca9f to eec0486 Compare October 27, 2024 15:12
@aimensahnoun aimensahnoun force-pushed the 1396-support-singlerequestproxy-in-the-request-network-sdk branch from 84fb664 to df6af29 Compare October 27, 2024 16:02
@aimensahnoun aimensahnoun force-pushed the 1396-support-singlerequestproxy-in-the-request-network-sdk branch from 40d7bba to 8df842f Compare October 28, 2024 11:17
@aimensahnoun aimensahnoun force-pushed the 1396-support-singlerequestproxy-in-the-request-network-sdk branch from 16dc636 to 1fd4723 Compare October 28, 2024 11:34
@aimensahnoun aimensahnoun force-pushed the 1396-support-singlerequestproxy-in-the-request-network-sdk branch from cd1d473 to 7a0cebf Compare October 28, 2024 12:15
@aimensahnoun aimensahnoun force-pushed the 1396-support-singlerequestproxy-in-the-request-network-sdk branch from 53cda1a to 635cc6f Compare October 28, 2024 12:38
@aimensahnoun aimensahnoun marked this pull request as ready for review October 28, 2024 12:48
@github-actions github-actions bot requested a review from kevindavee October 28, 2024 12:48
@aimensahnoun aimensahnoun force-pushed the 1396-support-singlerequestproxy-in-the-request-network-sdk branch from eba8d37 to 57665b0 Compare October 28, 2024 22:52
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: 3

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between 57665b0 and 8ac398d.

📒 Files selected for processing (1)
  • packages/payment-processor/test/payment/single-request-proxy.test.ts (1 hunks)
🧰 Additional context used
📓 Learnings (1)
packages/payment-processor/test/payment/single-request-proxy.test.ts (5)
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1453
File: packages/smart-contracts/test/contracts/ERC20SingleRequestProxy.test.ts:150-152
Timestamp: 2024-10-17T18:30:55.410Z
Learning: In `packages/smart-contracts/test/contracts/ERC20SingleRequestProxy.test.ts`, the skipped test `'should process a partial payment correctly'` exists intentionally to show that partial payments are supported without duplicating previous happy-path tests.
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1474
File: packages/payment-processor/test/payment/single-request-proxy.test.ts:251-270
Timestamp: 2024-10-28T16:03:33.215Z
Learning: When testing the payment-processor module, specifically in `packages/payment-processor/test/payment/single-request-proxy.test.ts`, it's acceptable to omit tests for partial payments if they have already been covered at the smart-contract level.
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1474
File: packages/payment-processor/src/payment/single-request-proxy.ts:156-160
Timestamp: 2024-10-28T15:52:05.032Z
Learning: When determining if a `SingleRequestProxy` is an `ERC20SingleRequestProxy` or an `EthereumSingleRequestProxy`, include a comment explaining that the presence of `tokenAddress` distinguishes between the two.
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1474
File: packages/smart-contracts/scripts/test-deploy-single-request-proxy.ts:14-32
Timestamp: 2024-10-28T20:00:25.780Z
Learning: In test files, such as `packages/smart-contracts/scripts/test-deploy-single-request-proxy.ts`, extensive error handling and input validation are considered unnecessary.
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1474
File: packages/smart-contracts/scripts/test-deploy-single-request-proxy.ts:9-13
Timestamp: 2024-10-28T20:00:39.160Z
Learning: In test files within `packages/smart-contracts/scripts`, high levels of type safety are not necessary; using `any` types is acceptable.

@aimensahnoun aimensahnoun force-pushed the 1396-support-singlerequestproxy-in-the-request-network-sdk branch from 8ac398d to a08c550 Compare October 28, 2024 23:02
@aimensahnoun aimensahnoun force-pushed the 1396-support-singlerequestproxy-in-the-request-network-sdk branch from a08c550 to 9cef13e Compare October 28, 2024 23:13
@kevindavee kevindavee removed their request for review October 29, 2024 02:53
…sdk' of github.com:RequestNetwork/requestNetwork into 1396-support-singlerequestproxy-in-the-request-network-sdk
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: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between 9cef13e and 47afd3b.

📒 Files selected for processing (2)
  • packages/payment-processor/src/payment/single-request-proxy.ts (1 hunks)
  • packages/payment-processor/test/payment/single-request-proxy.test.ts (1 hunks)
🧰 Additional context used
📓 Learnings (2)
packages/payment-processor/src/payment/single-request-proxy.ts (2)
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1474
File: packages/payment-processor/src/payment/single-request-proxy.ts:156-160
Timestamp: 2024-10-28T15:52:05.032Z
Learning: When determining if a `SingleRequestProxy` is an `ERC20SingleRequestProxy` or an `EthereumSingleRequestProxy`, include a comment explaining that the presence of `tokenAddress` distinguishes between the two.
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1474
File: packages/payment-processor/src/payment/single-request-proxy.ts:156-160
Timestamp: 2024-10-28T15:52:05.032Z
Learning: In the `payRequestWithSingleRequestProxy` function of `single-request-proxy.ts`, failing to retrieve `tokenAddress()` is expected for `EthereumSingleRequestProxy` contracts and is not an error.
packages/payment-processor/test/payment/single-request-proxy.test.ts (7)
Learnt from: aimensahnoun
PR: RequestNetwork/requestNetwork#1474
File: packages/payment-processor/test/payment/single-request-proxy.test.ts:138-139
Timestamp: 2024-10-29T08:02:02.600Z
Learning: When testing invalid requests in `packages/payment-processor/test/payment/single-request-proxy.test.ts`, it's acceptable to use `@ts-expect-error` to suppress TypeScript errors when the request intentionally lacks required properties.
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1474
File: packages/payment-processor/test/payment/single-request-proxy.test.ts:251-270
Timestamp: 2024-10-28T16:03:33.215Z
Learning: When testing the payment-processor module, specifically in `packages/payment-processor/test/payment/single-request-proxy.test.ts`, it's acceptable to omit tests for partial payments if they have already been covered at the smart-contract level.
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1453
File: packages/smart-contracts/test/contracts/ERC20SingleRequestProxy.test.ts:150-152
Timestamp: 2024-10-17T18:30:55.410Z
Learning: In `packages/smart-contracts/test/contracts/ERC20SingleRequestProxy.test.ts`, the skipped test `'should process a partial payment correctly'` exists intentionally to show that partial payments are supported without duplicating previous happy-path tests.
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1474
File: packages/payment-processor/src/payment/single-request-proxy.ts:156-160
Timestamp: 2024-10-28T15:52:05.032Z
Learning: When determining if a `SingleRequestProxy` is an `ERC20SingleRequestProxy` or an `EthereumSingleRequestProxy`, include a comment explaining that the presence of `tokenAddress` distinguishes between the two.
Learnt from: aimensahnoun
PR: RequestNetwork/requestNetwork#1474
File: packages/payment-processor/test/payment/single-request-proxy.test.ts:225-228
Timestamp: 2024-10-29T08:03:10.464Z
Learning: In 'packages/payment-processor/test/payment/single-request-proxy.test.ts' (TypeScript), when testing with an invalid proxy address, we should not use the zero address.
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1474
File: packages/smart-contracts/scripts/test-deploy-single-request-proxy.ts:14-32
Timestamp: 2024-10-28T20:00:25.780Z
Learning: In test files, such as `packages/smart-contracts/scripts/test-deploy-single-request-proxy.ts`, extensive error handling and input validation are considered unnecessary.
Learnt from: MantisClone
PR: RequestNetwork/requestNetwork#1474
File: packages/smart-contracts/scripts/test-deploy-single-request-proxy.ts:9-13
Timestamp: 2024-10-28T20:00:39.160Z
Learning: In test files within `packages/smart-contracts/scripts`, high levels of type safety are not necessary; using `any` types is acceptable.
🔇 Additional comments (1)
packages/payment-processor/test/payment/single-request-proxy.test.ts (1)

1-340: The test suite is comprehensive and well-structured

The tests effectively cover various scenarios for both Ethereum and ERC20 Single Request Proxies, including error handling, deployment, and payment processes. All functions are tested thoroughly, ensuring reliability and robustness of the new functionalities introduced.

Copy link
Member

@MantisClone MantisClone left a comment

Choose a reason for hiding this comment

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

Nice work. As always, thanks for putting up with all my comments

@aimensahnoun aimensahnoun enabled auto-merge (squash) October 29, 2024 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support SingleRequestProxy in the Request Network SDK
3 participants