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: Cross Chain Rates Recipient #671
feat: Cross Chain Rates Recipient #671
Changes from 2 commits
d94100e
55a94a9
da74efe
bb2eb6c
bf33106
c95f460
471f6f4
040cdfe
aabea26
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.
Is there any reason to generate unchecked
Addr
in caseget_raw_address
failed?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'm assuming if it fails then it's a cross-chain address. Maybe we should account for that possibility in
get_raw_address
itself? Feels like a topic worth discussing.@crnbarr93
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.
Handle potential errors when retrieving recipient's raw address
Using
unwrap_or
withAddr::unchecked
may mask errors fromget_raw_address
, potentially leading to invalid addresses being used without proper validation. It's important to handle theResult
returned byget_raw_address
explicitly to avoid unexpected behavior.Apply this diff to handle the error properly:
This change will propagate any errors from
get_raw_address
, ensuring that invalid addresses are not silently accepted.📝 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.
We should ensure cw20 isn't used for cross-chain here, maybe at the point of creating the rates recipient we validate?
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.
That would work when the
LocalRateValue
is flat, but when it's a percentage we'll have to handle it while processing the rate right?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.
Add test coverage for
is_cross_chain
method.The new method lacks test coverage. Please add tests to verify: