Fix bug where outputs are serialized twice if using `client.waitForCompletionOrCreateCheckStatusResponse`

Azure / azure-functions-durable-js

JavaScript library for using the Durable Functions bindings

https://www.npmjs.com/package/durable-functions

MIT License

128 stars 46 forks source link

Fix bug where outputs are serialized twice if using `client.waitForCompletionOrCreateCheckStatusResponse` #497

Closed hossam-nasr closed 1 year ago

hossam-nasr commented 1 year ago

When fixing #454 (in #462), a bug was introduced whereby outputs of orchestrations would be serialized twice if using client.waitForCompletionOrCreateCheckStatusResponse. This is because the createHttpResponse method used by waitForCompletionOrCreateCheckStatusResponse was serializing the output before passing it to the HttpResponse constructor, but the constructor itself also serializes the output. This PR fixes this bug.