Error when response is plain text / csv

[vdawg-git]

Description

The parsing of the response fails when the response is not json.
Subsequently responses of text/plain and text/csv throw an error, which is not returned, but remains uncaught.

Reproduction

Query an api endpoint which return text/*, like https://api64.ipify.org.

Checklist

• I’m willing to open a PR (see CONTRIBUTING.md)

[drwpow]

This is improved in 0.3.0. Now, the .json() response will fall back to .text(). Or you can override the default behavior with the parseAs option

[CEOehis]

@drwpow is there a parse-as flag for the openapi-typescript CLI?

For context, I have a remote schema that returns json but the Content-Type is text/plain. Openapi-typescript only checks for .json or .yml extension or content-type. Hence in this case, the schema is never parsed: https://github.com/drwpow/openapi-typescript/blob/5ca0255281d5341e1e859eb60db0054224c39ac5/packages/openapi-typescript/src/load.ts#L125-L136

[drwpow]

@drwpow is there a parse-as flag for the openapi-typescript CLI?

There’s not. It sounds like your server isn’t sending the right MIME types. The best solution is fixing that. But as a workaround you could write a short script that saves that file to a temporary local .json file and just running openapi-typescript locally.

Making the wrong “guess” of whether something is JSON or YAML is expensive and slows down everyone, hence that bit of code you referenced