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
Create configs #5677
Create configs #5677
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## feat/test-only-processor-node #5677 +/- ##
=================================================================
- Coverage 79.42% 79.25% -0.18%
=================================================================
Files 723 724 +1
Lines 95020 95203 +183
=================================================================
- Hits 75469 75452 -17
- Misses 14199 14399 +200
Partials 5352 5352
☔ View full report in Codecov by Sentry. |
) | ||
|
||
const ( | ||
genesisAddressWithStake = "erd10z6sdhwfy8jtuf87j5gnq7lt7fd2wfmhkg8zfzf79lrapzq265yqlnmtm7" |
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.
I would export all these constants. Even the private keys.
Maybe declare the private keys in hex format?
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.
done
return os.WriteFile(validatorsFile, buff.Bytes(), 0644) | ||
} | ||
|
||
func modifyFile(fileName string, f func(i []byte) ([]byte, error)) error { |
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.
not a big fan of providing a function pointer. Do we really need this or we can simplify the function signature?
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.
remove this function
Reasoning behind the pull request
Pre-requisites
Based on the Contributing Guidelines the PR author and the reviewers must check the following requirements are met:
feat
branch created?feat
branch merging, do all satellite projects have a proper tag insidego.mod
?