Would you please provide a sync version of parseString

[zszszsz]

It is strange to provide only async functions without providing sync versions of them. :-)

[zszszsz]

While what I find I am wrong is that the "async" version is not async at all.

Strange behavior, indeed.

I am going to close this issue,
but try this please,
and you will find the behavior of this function is strange:

(() => {
    var a;
    new require('xml2js').Parser().parseString('<xml>asdf</xml>', (e, r) => { a = r });
    console.log(a);
})();

[Leonidas-from-XIV]

I agree, but you can make the function async by setting the `async` param. The not-really-async behaviour was reported before but when I fixed it, much code broke becaus it just assumed that the function would be sync at heart, so I had to make it opt-in.

[ghostcode]

very confused!

[Leonidas-from-XIV]

Why are you very confused? I can attempt to explain my reasoning in other words it that clears it up for you.

[sirius1024]

@Leonidas-from-XIV I think it's confused because I have to told everyone of my colleagues that the function is SYNC actually……anyway, It won't be a big problem~
Thanks for your help.

[sirius1024]

@zszszsz so the right way to use this lib is:

let parsed;
parseString(msgBody.message, (err, rst) => {
     parsed = rst;
});
console.log(`${parsed}`);

BTW It did take me some time because in my mind I think everything is OK with await when I saw the callback function.

[Leonidas-from-XIV]

No, the right way is to use the callback and not exploit the fact that the callback is sync in the background which is an implementation detail and not guaranteed to stay working.

[sirius1024]

@Leonidas-from-XIV
all right, let's back to confused. 😂

[zszszsz]

@sirius1024 or maybe you are also interested in #380.

Anyway this issue is a closed one with proper solution.