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

Layout conflict check #4

Open
shogochiai opened this issue Sep 1, 2023 · 3 comments
Open

Layout conflict check #4

shogochiai opened this issue Sep 1, 2023 · 3 comments

Comments

@shogochiai
Copy link

shogochiai commented Sep 1, 2023

What is preventing you to have storage layout conflict checker with this nice scripts?

@phenix3443
Copy link
Owner

Didn't get your point, can you elaborate?

@shogochiai
Copy link
Author

Thanks for quick resp.

For example, you can take the version N and version N+1 in the script, and can use cheatcodes' ffi function to take target files as text. But such text analysis and comparison process is inefficient for Solidity code, so that you can bypass such logic to OpenZeppelin's storage layout checker.

Other workaround is taking two filenames as argument of the upgrade command, and see&compare those files before you run the upgrade script, then passing the check, run upgrade script with those target names.

@phenix3443
Copy link
Owner

I just started using solidity, openzepplin, so I don't really understand what you mean, can you illustrate this with a PR? Thank you very much.

Thanks for quick resp.

For example, you can take the version N and version N+1 in the script, and can use cheatcodes' ffi function to take target files as text. But such text analysis and comparison process is inefficient for Solidity code, so that you can bypass such logic to OpenZeppelin's storage layout checker.

Other workaround is taking two filenames as argument of the upgrade command, and see&compare those files before you run the upgrade script, then passing the check, run upgrade script with those target names.

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

2 participants