TypeError: bodyContent.match is not a function

[cpwr]

Hi! Postman is great, but I have some issues working with it
Neither the utility nor the Postman could not convert the API spec though it has passed the test and matches the requirements for the OpenAPI v3.0.3

$ openapi2postmanv2 -s ~/Documents/spec.yaml -o collection.json -p
Input file:  /home/user/Documents/spec.yaml
TypeError: bodyContent.match is not a function
    at getXmlVersionContent (/usr/local/lib/node_modules/openapi-to-postmanv2/lib/schemaUtils.js:2021:30)
    at Object.convertToPmBody (/usr/local/lib/node_modules/openapi-to-postmanv2/lib/schemaUtils.js:2034:11)
    at Object.convertRequestToItem (/usr/local/lib/node_modules/openapi-to-postmanv2/lib/schemaUtils.js:2557:21)
    at Object.convertChildToItemGroup (/usr/local/lib/node_modules/openapi-to-postmanv2/lib/schemaUtils.js:1035:19)
    at Object.convertChildToItemGroup (/usr/local/lib/node_modules/openapi-to-postmanv2/lib/schemaUtils.js:1023:18)
    at Object.convertChildToItemGroup (/usr/local/lib/node_modules/openapi-to-postmanv2/lib/schemaUtils.js:1023:18)
    at Object.convertChildToItemGroup (/usr/local/lib/node_modules/openapi-to-postmanv2/lib/schemaUtils.js:1023:18)
    at Object.convertChildToItemGroup (/usr/local/lib/node_modules/openapi-to-postmanv2/lib/schemaUtils.js:1023:18)
    at Object.addCollectionItemsUsingPaths (/usr/local/lib/node_modules/openapi-to-postmanv2/lib/schemaUtils.js:754:16)
    at /usr/local/lib/node_modules/openapi-to-postmanv2/lib/schemapack.js:346:23

The original spec file is here

Could someone help me to understand what the actual problem is?

[geromegrignon]

The input file spec.yaml doesn't match your link content format (json).

[cpwr]

@geromegrignon I couldn't get what is the difference, but I was able to do that with the same file using another app called portman:
the command was portman -l spec.yaml -o postman.json and after that I've successfully imported that collection.
What am I doing wrong?

[geromegrignon]

@cpwr the difference is your command implies you use a yaml file but providing a json file as a reference. It means your real situation can't be reproduced to understand your problem.

[cpwr]

@cpwr the difference is your command implies you use a yaml file but providing a json file as a reference. It means your real situation can't be reproduced to understand your problem.

it's only a name of the file. the content of it is what you can see by the link above.
I have checked that link returns valid JSON, and I have renamed the input file to spec.json, it doesn't make any difference.

[VShingala]

@cpwr Thanks for reporting the issue! We're working on the fix for this and we'll update this issue with any future updates.

[VShingala]

@cpwr We have fixed this issue in module version 4.9.0 and it'll soon be available with the upcoming App release.

[cpwr]

thanks for a fix! great!