Skip to content
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

include items json in csv export #2325

Closed
wants to merge 1 commit into from
Closed

Conversation

talvasconcelos
Copy link
Collaborator

Closes #2312

@talvasconcelos talvasconcelos added the enhancement Make something better label Mar 15, 2024
Copy link

codecov bot commented Mar 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.57%. Comparing base (116ca7f) to head (75878ae).
Report is 209 commits behind head on dev.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev    #2325   +/-   ##
=======================================
  Coverage   58.57%   58.57%           
=======================================
  Files          61       61           
  Lines        9218     9218           
=======================================
  Hits         5399     5399           
  Misses       3819     3819           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

name: 'items',
align: 'right',
label: 'Items',
field: row => (row.tag === 'tpos' && row.extra.details) || null
Copy link
Collaborator

@prusnak prusnak Mar 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is layering violation but I guess I agree with the quick fix like this.

Maybe we should have a way how an extension can tell LNbits which extra fields should be added in the future?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lnbits core should not know about a particular extension.
Suggestion: make the Export button a <q-btn-dropdown> with two options:

  • Basic Export
  • Detailed Export

It defaults to Basic Export. Mock UI:

image

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so but then, the detailed is not only for tpos, but it just packs all the info in the 'extra', is that it? if there's something there? this hack is just to include the details property that only exists, so far, in tpos

Copy link
Member

@arcbtc arcbtc Aug 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm with Stick, lets get this merged, and make something more sophisticated later.

@dni dni deleted the export_tpos_items_csv branch October 1, 2024 05:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Make something better
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature request] save title or ID of items sold in transaction history
4 participants