Generate CSV and Download it Client Side from the Browser 

objectToCSV (data) { // TODO: move to a lib. global plugin or mixin. const csvRows = [] // get headers const headers = Object.keys(data[0]) csvRows.push(headers.join(',')) // loop over values for (const row of data) { const values = headers.map(header => { const escaped = ('' + row[header]).replace(/"/g, '\\"') return `"${escaped}"` }) csvRows.push(values.join(',')) } // join and return all lines return csvRows.join(' ') }

Great video. But I do however have the same question as an absolute beginner.

Just figured, the function objectToCSV isn't an imported library but is written inside the function. He just writes it after calling it, around 4:22

You can pass tons of stuff to fetch. Including custom headers, which is where you'd put a token.

Hey, I know it was long time ago,but do you remember how did you solve the problem? Because i have same issue.

a CSV needs headers - your Data1 does not have any headers. What would you expect them to be in this example?

@@optikalefx umm I mean if data1 and data2 are totally different data, for example Data1 is producers Only shows the name Data2 is product It shows every single one product data with Id, price, cate, cateId

Pathfinder

which part? Happy to explain it more.

@@optikalefx Is the row the actual row? That constant that you declare what is it? Why when you make the return row[header] it returns every row in the desire position, sorry if I'm not clear explaining myself, I'm new at js, that function is pretty abstract for me 😜

@@sgomezj_ so in that loop, row is indeed each row of data. Then we're looping over the headers. Finally we are accessing the row object by each header. The reason we're doing this is to ensure that we get an Object that has the same number of keys in the same order. We can't trust the order of keys in an object to always be the same, but by looping over the headers array (where arrays do have guaranteed order) we can ensure the order of keys in the row object. This is important for a CSV so that the columns line up with the headers.

@@optikalefx Nice, thank you. I understood, so the rows have a default key which turns out to be the same of the headers, and that's why we can map over the headers array?

@@sgomezj_ It's not that it 'happens' to be that way. On line 10, we are getting the headers from the first row. So we're basically saying "whatever the keys of that first object are, let's make sure the rest of that object matches"