TS2339 - Property 'parsedbody' does not exist on HttpOperationResponse

[azure]

TS2339 - Property 'parsedbody' does not exist on HttpOperationResponse

[njannink]

I'm having the same issues:

error TS2554: Expected 0-1 arguments, but got 2.
error TS2339: Property 'parsedBody' does not exist on type 'HttpOperationResponse'.

any solution yet?

[RikkiGibson]

bodyAsJson was renamed to parsedBody in ms-rest-js and we recently updated the AutoRest generator to use this new name. The best solution is to use the latest ms-rest-js. Sorry for the inconvenience.

This has been fixed in the most recent preview versions of ms-rest-js and autorest.typescript.

[clouddra]

@daschult I am still encountering runtime errors with parsedBody. It always returns undefined even though bodyAsText is has valid json. Can you provide an example of the working cli command to run?

@clouddra If you use the following line on the command line:
autorest --typescript [email protected]/autorest.typescript@preview <the rest of your command>
then it will use the latest preview version of the AutoRest TypeScript generator. If you're not using the --generate-metadata command line argument, then you'll also need to go into your package.json file and update your ms-rest-js dependency to use the latest preview version as well (0.7.206 as of this comment).

[clouddra]

yes the property exists for me but it always return undefined. Is it unable to parse the response text?

[RikkiGibson]

If you look in the generated operation, e.g. getWithHttpOperationResponse(), do you see parsedBody being set in the code?

[clouddra]

parsedBody is not set. bodyAsText is set though.

[RikkiGibson]

I would try forcing using the latest generator and runtime with [email protected]/autorest.typescript@preview in autorest and npm i ms-rest-js@preview in your package.

[tomlm]

I see this if the REST API doesn't set the content-type to "application/json". In my case it was “application/octet-stream”, which causes the AutoRest generated code to not parse the content as json into the parsedBody property.

[RikkiGibson]

We might be able to do something like prefer the Content-Type given in "produces" in Swagger to the Content-Type we see at runtime. Do you mind opening an issue for this?