[Spike] Having 2x CSV export methods (JS-based and server-based) adds complexity with little/no benefit to merchants. Can we simplify?

Jinksi commented 2 days ago

Problem We currently have 2x implementations for generating CSV exports for reporting views, e.g. Transactions list, Payouts list, etc.

front-end JS-based CSVs are exported for small row counts (<25-100)
async service-generated for larger CSVs that are emailed to the accountholder

We should simplify this to reduce complexity, and maintenance footprint with the goal of improving the quality of the CSV export experience for our merchants.

Outcome The outcome of this spike should be a proposal with one or more solutions for what we could change to reduce the complexity of CSV exports.

haszari commented 2 days ago

@Jinksi What's the outcome of this issue – a spike or a proposal for what we could change?

Jinksi commented 1 day ago

Thanks @haszari, I've added outcome and updated the title to clarify that this is a spike.

Automattic / woocommerce-payments

[Spike] Having 2x CSV export methods (JS-based and server-based) adds complexity with little/no benefit to merchants. Can we simplify? #9764