[DO NOT MERGE] demo anypay v3
#720
Draft
+13,368
−274
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Session manager
…r consistency with other modules.
… import statements to include Hex type for better type safety, and streamline precondition data structure by adding chainId. Remove unnecessary mock provider setup for cleaner test code.
… isolation. Update import statements to include 'vi' for mocking capabilities, ensuring better control over provider behavior during tests.
…aTxnMonitor with useMetaTxnsMonitor for improved handling of multiple meta transactions. Remove deprecated monitoring logic and enhance status updates with detailed transaction information, including gas used and error handling.
… with origin call status handling. Remove deprecated state and effects related to meta transactions, streamlining transaction monitoring and improving clarity in status updates. Update related function names and UI bindings for consistency.
…plifying the transaction success handling. Adjust related success callback to focus on relevant transaction data, enhancing clarity in state management.
…tion handling. Integrate useEstimateGas hook for accurate gas limits, implement error handling for estimation failures, and update UI to reflect gas estimation status.
…figurationAddress function to accept calls and chainId directly
… suite. Implement scenarios for single and multiple operations, ensuring expected addresses match Go test results.
… IntentCallsPayload, enhancing clarity and consistency in transaction handling. Update related functions and state management to accommodate new payload structure, ensuring compatibility with recent API changes.
…nhance UI with improved styling for better readability and clarity in transaction data presentation.
…visibility. Improve UI styling for better readability and organization of transaction data.
…lations. Update AnyPay tests to utilize isAddressEqual for address verification and add multi-chain intent operation scenarios, ensuring deterministic address calculations align with expected results.
…st expected address verification. Enhance test scenarios for multi-chain intent operations, ensuring alignment with deterministic address calculations.
…onstants for consistency across the application. Ensure alignment with recent changes in address verification and intent configuration.
…figuration verification, ensuring consistency with recent address changes.
…ute for improved debugging. Added console logs to display main signer and calls payload during intent address calculations.
…ent parameters. Implement validation checks for input fields and update AnyPay tests to cover new hashing functionality, ensuring accurate hash generation for single and multiple calls.
…tination tokens, enhancing input validation and ABI encoding. Update tests to reflect new parameter structure and ensure accurate hash generation for single and multiple calls, including detailed debug logging for better traceability.
… adjustments for intent hashing. Modify test cases for single and multiple calls, ensuring alignment with recent changes in hash generation logic.
…sh generation logic. Update cumulative hash calculation for destination calls and adjust ABI schema. Modify AnyPay tests to reflect changes in expected hash values and error handling behavior.
… configuration. Add console logs for debugging address calculations in multiple test cases, ensuring alignment with recent changes in address verification logic.
…oved validation and ABI encoding. Update tests to incorporate nonce in input validation and adjust expected hash values accordingly, ensuring consistency with recent changes in hash generation logic.
…. Enhance intent configuration handling by incorporating lifiInfos in relevant functions and ensure proper error handling. Update API schema to include new lifiInfos structure for improved data flow.
…etails. Include raw JSON view of lifiInfos to enhance data visibility and debugging capabilities.
…information. Implement validation for input parameters and update tests to cover various scenarios, including error handling for empty inputs and zero addresses.
…Infos and attestationSigner parameters. Update HomeIndexRoute and tests to accommodate changes, ensuring proper handling of undefined values and enhancing intent configuration logic.
…oach for constructing the Merkle tree. This change improves performance and readability by eliminating recursion, while maintaining the same functionality for handling topology members.
…ifiInfos as an argument, improving intent configuration logic. Update related calls and logging to ensure proper handling of Lifi information throughout the component.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.