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

Investigate if we should keep Declare cheatcode #2170

Open
cptartur opened this issue Jul 4, 2023 · 0 comments
Open

Investigate if we should keep Declare cheatcode #2170

cptartur opened this issue Jul 4, 2023 · 0 comments

Comments

@cptartur
Copy link
Member

cptartur commented Jul 4, 2023

@MaksymilianDemitraszek suggested that we should remove declare cheatcode entirely, and implicitly declare all contracts from the project when running a test runner.

This might be a good approach, but there are some open questions:

  • how should declaring work if the user doesn't know the class hash
  • how to actually get the class hash of declared contract
  • what in the case where user doesn't want to have their contract declared automatically for whatever testing reasons
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

No branches or pull requests

1 participant