Export to CSV

[TriPSs]

Is your feature request related to a problem? Please describe.
When exporting data we now have to create endpoints for all the data types, would be easier if we, just like aggregation, can enable this.

Have you read the Contributing Guidelines?

Yes

Describe the solution you'd like
a <DTO>Export method that accepts the same filters and additionally a map for the columns { field: string, headerName: string } (if not provided use field names) and format = ExportFormat where ExportFormat only accepts CSV for now.

Describe alternatives you've considered
Creating a service/resolver class for each data type ourselfs.

Additional context
Add any other context or screenshots about the feature request here.

[lume-code]

Is there any ETA or active work going on for this? I was actually looking for this.

[TriPSs]

Not yet, still want it but did not have any time for it yet.

[lume-code]

@TriPSs If we were to do this ourselves outside the library, is there any way to utilize and filter based on the same FilterInput that nests-query creates on the fly? If yes, and you can give me a tip on how it can be achieved/or impossible (e.g I shouldn't pursue it), that would be great. Thanks.

[TriPSs]

@lume-code yes, you could copy the read resolver and remove the pagina from it, then everything that works in query many will work with the CSV export. Use it to fetch the data and then create the CSV (based off the format = ExportFormat).

[lume-code]

@TriPSs Great, Thanks, I will give it a shot😊

[lume-code]

This was my attempt at an export resolver that works for most parts except for the relation retrieval part:

https://gist.github.com/lume-code/5a0e90a2b6526e4a23ed98c11335b445