-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
invariant: #6694 add preserve_state
config
#7219
Conversation
…e state (e.g. using cheatcodes like roll, warp), see foundry-rs#6694 - active only in conjunction with fail_on_revert true
See also #5444, so deferring to @Evalir on how this should be implemented. Committing/preserving state is more intuitive and should be the default though—assuming the performance issue is resolved, what is the reason you'd want to disable it? It should also apply whether or not |
the only reason for disabling by default and applying with |
preserve_state
configpreserve_state
config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that makes sense and a reasonable usecase
lgtm, pending @Evalir
Motivation
Solution
call_raw_committing
ifpreserve_state
andfail_on_revert
enabled