Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat(server): Allow calling back into the application struct in PostSetup. #19455
feat(server): Allow calling back into the application struct in PostSetup. #19455
Changes from 3 commits
b6fc778
15454f6
1a0ec34
2461cff
3cf059b
68e9430
ca37db5
74f2d5e
aed949b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check failure on line 6 in client/snapshot/cmd.go
GitHub Actions / golangci-lint
Check failure on line 6 in client/snapshot/cmd.go
GitHub Actions / Analyze
Check failure on line 7 in client/snapshot/cmd.go
GitHub Actions / golangci-lint
Check failure on line 7 in client/snapshot/cmd.go
GitHub Actions / Analyze
Check failure on line 9 in client/snapshot/export.go
GitHub Actions / golangci-lint
Check failure on line 9 in client/snapshot/export.go
GitHub Actions / Analyze
Check failure on line 10 in client/snapshot/export.go
GitHub Actions / golangci-lint
Check failure on line 10 in client/snapshot/export.go
GitHub Actions / Analyze
Check failure on line 13 in client/snapshot/restore.go
GitHub Actions / golangci-lint
Check failure on line 13 in client/snapshot/restore.go
GitHub Actions / Analyze
Check failure on line 14 in client/snapshot/restore.go
GitHub Actions / golangci-lint
Check failure on line 14 in client/snapshot/restore.go
GitHub Actions / Analyze
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.
The
start
function's adaptation to use generics is well-implemented. However, consider adding error handling for thestartStandAlone
andstartInProcess
calls to ensure any errors during the startup process are appropriately managed.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.
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.
gently ping on this one
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.
@itsdevbear, it should still be committed as you've forced pushed your last commit, which removed this.
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.
The
InPlaceTestnetCreator
andtestnetify
functions introduce complex logic for creating a testnet from the current state. It's crucial to ensure that these functions are well-documented and that their impact on the application's state is clearly understood by developers. Consider adding more inline comments explaining the steps involved, especially in thetestnetify
function, to improve maintainability.+ // Explanation of the logic and its impact on the application's state
Check failure on line 23 in server/util_test.go
GitHub Actions / golangci-lint
Check failure on line 23 in server/util_test.go
GitHub Actions / Analyze
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.
The import statement for
types
is duplicated as bothgithub.com/cosmos/cosmos-sdk/server/types
andservertypes "github.com/cosmos/cosmos-sdk/server/types"
. This redundancy could be eliminated to improve code clarity and maintainability.- "github.com/cosmos/cosmos-sdk/server/types"
Committable suggestion
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.
Good point from the bot
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.
@julienrbrt: Thank you for acknowledging the point! If there's anything more I can help with, please let me know.
\ (^-^) /
Check failure on line 24 in server/util_test.go
GitHub Actions / golangci-lint
Check failure on line 24 in server/util_test.go
GitHub Actions / Analyze