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

meta(cheatcodes): tracking issue for cheatcode improvements #4439

Open
mds1 opened this issue Feb 27, 2023 · 1 comment
Open

meta(cheatcodes): tracking issue for cheatcode improvements #4439

mds1 opened this issue Feb 27, 2023 · 1 comment
Labels
A-cheatcodes Area: cheatcodes C-forge Command: forge Cmd-forge-test Command: forge test T-meta Type: meta

Comments

@mds1
Copy link
Collaborator

mds1 commented Feb 27, 2023

Component

Forge

Describe the feature you would like

This issue tracks general cheatcode improvements. Items are roughly ordered by my opinion of priority, both at the header-level and the bullet-level. I say "roughly ordered" because some items are much bigger scope than others so having a strict ordering doesn't make much sense.

Refactors, Higher Priority

Medium Priority

Lower Priority

Additional context

No response

@PaulRBerg
Copy link
Contributor

PaulRBerg commented May 4, 2023

Can we bump the priority of #4762 up to "Medium"?

  1. It's a subtle cause for failing tests, which can result in long-winded debugging sessions.
  2. For complex code bases with many test contracts, it is frustrating to have to ensure that certain dummy contracts are never considered for reverts. The refactors required to skirt around this limitation can be non-trivial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-cheatcodes Area: cheatcodes C-forge Command: forge Cmd-forge-test Command: forge test T-meta Type: meta
Projects
Status: Todo
Development

No branches or pull requests

3 participants