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
refactor: update cctx status to object to split error message into
error
andrevert_error
#3326base: develop
Are you sure you want to change the base?
refactor: update cctx status to object to split error message into
error
andrevert_error
#3326Changes from 14 commits
dd6aa99
7380d27
66170ae
542b448
9e20402
889a815
1948197
5af3f2c
3a26b7e
2ed02a9
acf9793
a72b3ef
2fb8d5d
2045d3d
afe7be1
af8fa7d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This struct is only used internally, and not saved to the state.
In my opinion, the code looks cleaner using this object rather than three strings as arguments. But it can be changed to that if needed
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.
If it's used internally we don't need a proto definition and it can be an internal type
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.
Defined this at the proto level as we we can refactor the Status object in the future to use this directly instead of defining three fields .
I wanted to get reviews on this pr before creating an issue.
I can refactor to defining a type, though, if its still needed
Check warning on line 379 in x/crosschain/keeper/cctx_orchestrator_validate_outbound.go
Codecov / codecov/patch
x/crosschain/keeper/cctx_orchestrator_validate_outbound.go#L376-L379
Check warning on line 399 in x/crosschain/keeper/cctx_orchestrator_validate_outbound.go
Codecov / codecov/patch
x/crosschain/keeper/cctx_orchestrator_validate_outbound.go#L397-L399
Check warning on line 415 in x/crosschain/keeper/cctx_orchestrator_validate_outbound.go
Codecov / codecov/patch
x/crosschain/keeper/cctx_orchestrator_validate_outbound.go#L412-L415
Check warning on line 51 in x/crosschain/keeper/evm_deposit.go
Codecov / codecov/patch
x/crosschain/keeper/evm_deposit.go#L51