fix: make getUtxos address/maxUtxos filter work#278
Merged
Conversation
pedroferreira1
commented
Aug 5, 2025
|
|
||
| const event = makeGatewayEventWithAuthorizer('my-wallet', null, null, { | ||
| addresses: [ADDRESSES[1]], | ||
| 'addresses[]': [ADDRESSES[1]], |
Member
Author
There was a problem hiding this comment.
This test show that it used to work.
andreabadesso
approved these changes
Aug 5, 2025
tuliomir
approved these changes
Aug 5, 2025
9428bc8 to
793a3aa
Compare
This was referenced Nov 17, 2025
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
The filter by address and max utxos is not working in the utxos/outputs API. It seems like a recent upgrade changed the way lambda gets multi value query string.
Acceptance Criteria
Checklist
master, confirm this code is production-ready and can be included in future releases as soon as it gets merged