-
Notifications
You must be signed in to change notification settings - Fork 156
buidler-refactor #164
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
buidler-refactor #164
Conversation
thegostep
commented
Aug 28, 2020
•
edited
Loading
edited
- migrate tests
- convert to typescript
- add use of fixtures https://ethereum-waffle.readthedocs.io/en/latest/fixtures.html
- add use of mocks https://ethereum-waffle.readthedocs.io/en/latest/mock-contract.html
- update deploy scripts
- remove manual steps
- add manager-owner pattern
- add zeppelin sdk-cli compatibility
- update CI
- update travis
- update precommit hooks: https://prettier.io/docs/en/precommit.html
- add crytic: https://github.com/crytic/slither/wiki/Upgradeability-Checks
5e45b6a
to
1e0fbdf
Compare
@thegostep can you make the test file renames register as moves rather than deletion/additions. |
1e0fbdf
to
a34b4e9
Compare
@nithinkrishna I took a crack at this - unfortunately I don't think it is possible for git to track diffs between js and ts files. Instead I've staged the files as js so that the diffs work and then converted to ts in separate commit |
a34b4e9
to
886d971
Compare
As far as I can see this doesn't change any of the contracts. It only updates the testing environment. I like the buidler + ethers framework a lot after using it for a couple of projects. Will wait for @brandoniles or @ahnaguib to have another look before merging |
Here is a great tutorial on process for upgrades: https://forum.openzeppelin.com/t/openzeppelin-upgrades-step-by-step-tutorial-for-hardhat/3580 |
d574541
to
562f17d
Compare
562f17d
to
f786051
Compare
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.
Thanks Stephane, I will always support typed language!
I see that package-lock.json is removed and node_modules is added to gitignore. Will we still get reproducible builds?
AFAICT, the only changes to the solidity files are formatting. I assume this matches the new linter settings. As a general note, I'd recommend separating the code changes from the test changes when the behavior is meant to be the same. It gives more confidence that neither introduces problems on their own.
Yes - I switched the package manager from npm to yarn. See yarn.lock for version locking |
Fair - I can split into seperate PRs if you prefer. Just say the word ✨ |
following @brandoniles suggestion, this PR is superseded by #176 and #177 |