-
Notifications
You must be signed in to change notification settings - Fork 638
chore: export node package errors #3056
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
Conversation
Thanks @TropicalDog17, we will be reviewing the PR |
Hi @TropicalDog17, seems it's failing on linting. Could you please check it ? For reference: https://github.com/cometbft/cometbft/blob/main/CONTRIBUTING.md#formatting--linting |
Thanks @andynog, I've fixed the linting issue and |
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.
Hi @TropicalDog17, just had a chance to review the PR. I've made some small changes on comments and parameter order. Overall it's good, but in setup.go
there are still many errors that were not exported or the exported error was not used, like in line 64
if err != nil {
return ChecksummedGenesisDoc{}, fmt.Errorf("couldn't read GenesisDoc file: %w", err) }
Could you please ensure these other errors in setup.go
are also exported ? Thanks !
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 @TropicalDog17 ❤️
the fact that not all errors are exported shouldn't block us from merging this PR
Partially addresses #1140
PR checklist
.changelog
(we use unclog to manage our changelog)docs/
orspec/
) and code comments