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!: implement StateOverride as a safer alternative to working with Map<Address, AccountOverride> directly #106

Merged
merged 3 commits into from
Mar 27, 2024

Conversation

ArtificialPB
Copy link
Member

Description

Also fixes a bug with apply/mergeChanges where it would keep a reference to override from other, which would mean that subsequent apply calls would modify the original value, possibly leading to hidden bugs.

Solution

@ArtificialPB ArtificialPB requested a review from kustrun as a code owner March 27, 2024 15:21
@ArtificialPB
Copy link
Member Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ArtificialPB and the rest of your teammates on Graphite Graphite

@ArtificialPB ArtificialPB changed the title implement StateOverride as a safer alternative to working with Map<Address, AccountOverride> directly feat!: implement StateOverride as a safer alternative to working with Map<Address, AccountOverride> directly Mar 27, 2024
@ArtificialPB ArtificialPB merged commit 6d399e7 into master Mar 27, 2024
1 check passed
@ArtificialPB ArtificialPB deleted the fix/state-overrides branch March 27, 2024 20:26
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.

1 participant