fix!: allow empty memos (NULL op returns) #80
Merged
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.
BREAKING CHANGE
null
is now the placeholder value for objects that complete the output interfacePreviously an output that looked like this would be considered a payment to 'xxx'
Between this and #74 (which allows burn memos), it will now throw an error:
Also, it seems that there may have been a regression of #56, because this does the same that that says in the title.
Tested, working
https://trpc.digitalcash.dev/#?method=getrawtransaction¶ms=["79e822ae946a2babb141291c052da999d3987f0529cbb3cece02cc2377997a59",1]&submit