-
Notifications
You must be signed in to change notification settings - Fork 11
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
doc: add style guide #660
doc: add style guide #660
Conversation
|
|
||
### Member functions | ||
|
||
For member functions, use the following default rules to order them: |
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.
"default rules" -- I'm assuming this means it's ok to deviate if it makes sense? Would be good to make it more explicit if possible
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.
Addressed in d1a250f
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 for this! I left one comment, but approving to unblock merging
Co-authored-by: Igor Matuszewski <[email protected]>
d1a250f
to
9c8ea3b
Compare
$ npx hardhat node AccountsAccount #0: 0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266 (10000 ETH) Account #1: 0x70997970c51812dc3a010c7d01b50e0d17dc79c8 (10000 ETH) |
Proposal for adding guidelines around code style