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: get write tx for single message #6003

Merged
merged 17 commits into from
Apr 15, 2024

Conversation

LayneHaber
Copy link
Contributor

Description

Fixes review comments left in #5926 by:

  • making x1 return a WriteTransaction for a single message
  • updating the processor config to return a WriteTransaction

Before merging, we need to ensure that lighthouse will pick up the spoke messages as well.

Type of change

  • Docs change / dependency upgrade
  • Configuration / tooling changes
  • Refactoring
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Requires changes in customer code

High-level change(s) description - from the user's perspective

Related Issue(s)

Fixes

Related pull request(s)

processorFunctionName: string;
contractAddress?: string;
contractAbi?: string[];
getWriteTransaction: (params: GetProcessArgsParams) => Promise<WriteTransaction | undefined>;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Like this pattern.
Concerned that this might cause regression on other (non- XLayer) changes, since this touches processFromRoot on all chains.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

possible, but that's why I grouped the write tx generation in a single function and kept the original getArgs utils

@LayneHaber
Copy link
Contributor Author

coverage issues will be resolved in base branch, merging

@LayneHaber LayneHaber merged commit 2a87d59 into 5834-x1-for-mainnet Apr 15, 2024
21 of 22 checks passed
@LayneHaber LayneHaber deleted the 5834-subtask-lighthouse branch April 15, 2024 21:05
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.

3 participants