refactor: reduce code duplication for assertion cheats and introduce legacy_assertions flag#8251
Merged
refactor: reduce code duplication for assertion cheats and introduce legacy_assertions flag#8251
legacy_assertions flag#8251Conversation
DaniPopes
approved these changes
Jun 25, 2024
Member
Author
yeah, we'd need it for complete support of the |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Updating code for 100+ impls would've been painful, so decided to clean this up with a macro
legacy_assertionsdoesn't print any info about failure at the moment, just returns successful resultTo print logs we'd need #8181 to push them to
LogCollector. We could've collected a separate logs list onCheatcodes, but it's unclear how to ensure correct ordering