Export to CSV

[pandeymangg]

What does this PR do?

Fixes #253

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Chore (refactoring code, technical debt, workflow improvements)
• Enhancement (small improvements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change adds a new database migration
• This change requires a documentation update

How should this be tested?

• Test A
• Test B

Checklist

• Read the contributing guide
• Self-reviewed my own code
• Commented on my code in hard-to-understand bits
• Ran pnpm build
• Checked for warnings, there are none
• Removed all console.logs
• Merged the latest changes from main onto my branch with git pull origin main
• My changes don't cause any responsiveness issues
• Updated the Formbricks Docs if changes were necessary

[vercel]

@pandeymangg is attempting to deploy a commit to the formbricks Team on Vercel.

A member of the Team first needs to authorize it.

[mattinannt]

@pandeymangg Thanks a lot for your work and the PR 💪😊
I am having trouble getting my browser (Chrome as well as Firefox) to download the CSV file due to this browser error after clicking the "Export to CSV" button:

You are not allowed to load local resource: blob:nodedata:aaa52f51-f541-485f-897b-26824ae55e70

Johannes gets the same error. Can you reproduce this?
According to chatGPT, this is due to a security restriction in modern browsers to prevent downloading from the local file system, and it suggests creating a blob of type csv first and then downloading it.
Once this is fixed I can check the PR and CSV results properly 💪.

[pandeymangg]

@mattinannt I'm not able to reproduce the same error in my browsers, neither chrome nor firefox. And I have actually created the blob of type csv first before making the URL object, I'm not sure what the exact problem is, I'll try to debug this and update the PR

[jobenjada]

@mattinannt The CSV download is fixed and working well. No more remarks from my end, please merge when you agree.

[mattinannt]

@pandeymangg thanks a lot for the changes 😊 The CSV now works great on my end, too 💪
The code also looks great :-)
I would like you to make some minor improvements to the exported CSV before merging the changes.

---

can you please use a dynamic file-name for the survey. e.g. the export of the survey named My Survey should be my_survey_responses_2023_06_15.csv

In this filename:

my_survey is a URL-friendly version of "My Survey". Spaces are replaced with underscores or hyphens, and all letters are lowercased.
responses specifies what kind of data is in the file.
2023_06_15 is the date when the file was created. This can be especially useful if there are multiple exports over time.

---

You currently have a Date Submitted submitted column in the CSV but for a more detailed data analysis it would be helpful to have the date-time. Can you please change the name of the column to Timestamp and the Date to an ISO-String?

[pandeymangg]

@mattinannt Got it, I'll make these changes and update the PR.

Apart from these changes, I was also considering of changing the package that I'm using to convert json to csv. I'm currently using the json2csv/plainjs package, but I think a better alternative could be json2csv/node because all the conversion from json to csv is happening on the server only. What do you say?

Reference: https://juanjodiaz.github.io/json2csv/#/parsers/node-async-parser

[mattinannt]

@mattinannt Got it, I'll make these changes and update the PR.

Apart from these changes, I was also considering of changing the package that I'm using to convert json to csv. I'm currently using the json2csv/plainjs package, but I think a better alternative could be json2csv/node because all the conversion from json to csv is happening on the server only. What do you say?

Reference: https://juanjodiaz.github.io/json2csv/#/parsers/node-async-parser

Thanks for pointing this out. I think switching to json2csv/node is a good idea since it doesn't block the javascript event loop.

[mattinannt]

@pandeymangg Awesome, works great 💪 Thanks for this contribution; I'm going to merge the feature now 😊