Use case emptyFieldValue

[joostdebruijn]

Background Information

• Module Version: 3.0.0
• Node/Browser Version: 11.6.0

The issue I'm reporting is with:

• json2csv
• csv2json

I have...

• searched to see if an issue has already been reported.
• verified that my JSON/CSV data is valid (using something like http://jsonlint.com or https://csvlint.io/).
• tried upgrading to the latest version of json-2-csv (since the issue may already be fixed).

Actual Behavior

In 3.x the emptyFieldValue is removed. The upgrade guide says "Please open an issue on the GitHub repository mrodrig/json-2-csv if you have a valid use case for this option to be implemented.", so here it is!

Expected Behavior

We use the json2csv function for exporting data from a database to CSV for end-user purposes. End-users mostly use those CSV's in Excel. Previously we used the option emptyFieldValue with the value '' to replace values like null to an empty field in the CSV. In 3.0.0 those fields are now filled with null, that could be relevant when converting it back to json, but not for end-user display.

[mrodrig]

Hi @joostdebruijn! Thanks for opening up this issue. That's a completely valid use case and I can completely understand why it is important to convert those values over for end-users. I took a quick look and it looks like I should be able to get the option added in tonight after work. I'll comment back to let you know if I was able to get it added and published out to NPM.

Thanks again and sorry for any inconvenience this may have caused!

[mrodrig]

Hi @joostdebruijn - I pushed out version 3.1.0 which will have the emptyFieldValue option added in. Please let me know if you run into any issues with it or if there are any other issues that you run into with the module.

Thanks!

[joostdebruijn]

Thanks for the very quick resolution! It works fine now, however at src/utils.js:138 there is a console.log that logs all values to the console. I think that should be removed.

[mrodrig]

@joostdebruijn Sorry for the console log sneaking through. I merged your fix and added no-console to the linter so it won't happen again. Both are released in 3.1.1 on NPM. Thanks!