Feature: export wallet transactions #1043
No reviewers
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#1043
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "export-csv"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Changes
FileExporter
.JSON
andCSV
format #976util/parseTransactions.js
:Parse relevant data to be exported (Wallet transactions, bookmarks, playlist...)
Was able to export to both csv and json. Can it default to csv by default? Looks like it adheres to the filter chosen too, great!
I'm not sure if I'd put the export button on the Overview page, maybe just history? Maybe put it on the same line as Transaction History, but right justified? @kauffj, thoughts?
Thanks @btzr-io! this is great, I am fine with merging this (unless someone has a concrete suggestion for how to change it, where to place the button, etc)
Please resolve merge requests first, though :)
@liamcardenas conflicts fixed:
3505e43
df1f67c