-
Notifications
You must be signed in to change notification settings - Fork 3
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: show podcasting info in transactions #146
base: master
Are you sure you want to change the base?
Conversation
Can we get rid of the seemingly duplicate "description" & "message" here? Or could they be different? |
I think we should change this in the Hub, if the transaction already has the tlv records/boostagram, then it doesn't make sense to change the description of the transaction to the one fetched from tlv records right? Similarly we do this during zap requests made in the rails app, we change the description to the content from the zap... (this is should also be changed I feel) |
7e557d4
to
5a7afdf
Compare
5a7afdf
to
f340165
Compare
|
||
export function Transaction() { | ||
const { transactionJSON } = useLocalSearchParams() as unknown as { | ||
transactionJSON: string; | ||
}; | ||
const transaction: Nip47Transaction = JSON.parse(transactionJSON); | ||
const getFiatAmount = useGetFiatAmount(); | ||
const rawMetadata = transaction.metadata; |
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 part could potentially be memoized. Otherwise the records are parsed with every render...
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.
One little nitpick, otherwise 👍
tACK
Description
Fixes #16
This adds boostagram tlv record info only. We don't show other info in the Hub, is it worth showing the other custom record information here?
Screenshots