Question: How to use it in async/await fasion? about jsonexport HOT 5 CLOSED

Yes, thank you. I'm good with wrapping it with new Promise(), and jsonexport is really helpful for converting json to csv in my project.

from jsonexport.

NOTE: previous comment was me signed in from my work account

from jsonexport.

I don’t use await new Promise, I use just new Promise with a then attached to it.

But otherwise, I promise jsonexport relatively the same way you demonstrated above

from jsonexport.

Yes I agree await new Promise is ugly, so is there any better way to improve it?

For example, the json-2-csv repo support the traditional node js fasion

var json2csvCallback = function (err, csv) {
    if (err)
        throw err;
    console.log(csv);
};
converter.json2csv(documents, json2csvCallback);

and at the same time, it exposes an async/await fasion:

const csvData = await converter.json2csvAsync(data);
console.log(csvData)

Is this repo jsonexport exposes a -Async like method as well?

from jsonexport.

This library has no async function beyond a callback as far as I know.

I’m an Angular guy and I use Observables over Promises but absolutely I still use Promises.

One day it might be Promises someone needs. Another day it’s Observables. And then another day someone wants functional Ramda like access.

In whatever project I’m on that needs jsonexport, I just add one function that wraps jsonexport in an Observervable. I’ve even used the promise package Bluebird to promisify jsonexport (bluebird has one function called promisify that converts any callback to a promise).

To close, the ol saying “if it ain’t broke don’t fix it” comes to mind. That may come off as a lazy statement but I’ve never felt the need to “improve” this package (with async abilities)

from jsonexport.