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

fix: do not require --sender with --unlocked #7742

Merged
merged 2 commits into from
Apr 20, 2024
Merged

Conversation

klkvr
Copy link
Member

@klkvr klkvr commented Apr 20, 2024

Motivation

Closes #4822

Solution

We now do not require users to explicitly provide senders for --unlocked and resolve them from collected transactions instead:

SendTransactionsKind::Unlocked(required_addresses)

@klkvr klkvr changed the title fix: do not require --sender with --unlocked fix: do not require --sender with --unlocked Apr 20, 2024
@DaniPopes
Copy link
Member

DaniPopes commented Apr 20, 2024

Can we add a CLI test for this with anvil?

@klkvr klkvr requested a review from Evalir as a code owner April 20, 2024 21:40
@klkvr klkvr merged commit 6f2668f into master Apr 20, 2024
19 checks passed
@klkvr klkvr deleted the klkvr/unlocked-sender branch April 20, 2024 22:56
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.

Allow forge script --unlocked without --sender
2 participants