The main use case when anybody brings this up is using the data in a spreadsheet, but every major spreadsheet application can just connect to the database directly (it's PostgreSQL) and leave Typica out of that side of things. Similarly, psql can output CSV through the \copy metacommand if you wanted to use a spreadsheet that runs in your web browser instead of a local application. Both of those are probably better choices.
Personally I'd rather get the feature requests of what deficiency in Typica is leading them to the idea that they want this data in a spreadsheet to begin with and see if it makes sense to improve Typica with regard to that use case.
On the other hand, I can also see how it could be useful to have something built in with a lower learning curve for weird one off data exploration tasks that don't really fit the model of a pre-canned report.
So, CSV export on all reports: not happening. CSV export on some reports: probably not happening but maybe. CSV export from some kind of query explorer: decently likely if I can figure out an interface that's not completely awful.
CSV
The main use case when anybody brings this up is using the data in a spreadsheet, but every major spreadsheet application can just connect to the database directly (it's PostgreSQL) and leave Typica out of that side of things. Similarly, psql can output CSV through the \copy metacommand if you wanted to use a spreadsheet that runs in your web browser instead of a local application. Both of those are probably better choices.