feat: transaction metadata (zaps, payerdata, comment) #678
+136
−39
Conversation
This file contains 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
rolznz
reviewed
Sep 19, 2024
| Boostagram *Boostagram `json:"boostagram,omitempty"` | ||
| } | ||
|
|
||
| type Metadata = map[string]interface{} | ||
| type Metadata struct { |
There was a problem hiding this comment.
Transaction metadata can be anything. It could contain these fields. With this change it probably breaks other types of metadata
rolznz
reviewed
Sep 19, 2024
| Tags [][]string `json:"tags"` | ||
| } | ||
|
|
||
| type PayerData struct { |
There was a problem hiding this comment.
PayerData can also contain anything. We just know about these fields
|
what's the status on this one? |
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.
Fixes #577
Just adds the backend, needs design input to handle zaps and payerdata on the frontend