Input not taking JSON as valid data

[Zino-ctrlZ]

Hi, I'm making use of Converter.convert from openapi-to-postmanv2 in typescript running node20. The index.d.ts file has the data property in Input set to string.
i.e in the build file,

export interface Input {
    type: "file" | "string" | "json";
    data: string;
}

so I'm getting an error when trying to pass an object to in in the data property, so the below fails

Converter.convert({type: "json", data:"data_as_json"},{}, ()=>{})

is there no support for passing data as json in node ?

[Zino-ctrlZ]

Can someone confirm if this package supports esm modules ?

[SharmilaChoudhary]

const examplejson = {
openapi: '3.0.0',
info: {
title: 'Sample API',
version: '1.0.0',
},
paths: {
'/users': {
get: {
summary: 'Get all users',
responses: {
'200': {
description: 'A list of users',
},
},
},
},
},
};

Converter.convert(
{ type: 'json', data: JSON.stringify(examplejson) },
{},
() => {}
);

pass your json using JSON.stringify()

[Zino-ctrlZ]

my json has circular dependency so JSON.strinfgify will throw an error but also jSON.stringify returns a string. so although you state the type as json, youre still passing string in the in the data property of input .

Importing the package as commonjs allows me to pass a json as data without typescript getting mad at me, but the converter uses JSON.stringify internally when the type is json so the convert doesn't work anyways..

I handled the circular dependency externally using fast-safe-stringify (it replaces circular dep with [circular]. This works and generates a collection. I put that in quotes because the resulting collection.json fails when trying to import it to postman. I just get an import failed

[HabiburRahmaan]

Hi @Zino-ctrlZ
When converting Swagger 2.0 specifications to Postman Collections using the postman-collection or swagger2-postman2 NodeJS module, the UserError: Specification must contain a semantic version number of the OAS specification occurs. This happens because the converter expects the openapi field instead of the swagger field for Swagger 2.0 specs. While changing swagger: "2.0" to openapi: "2.0" bypasses the error, it breaks the output. OpenAPI 3.x conversions work seamlessly.

Suggested Fixes:

Ensure the converter library is updated to a version that properly supports Swagger 2.0 via the swagger field.

If the issue persists, file a bug report with the library maintainers to address the incorrect validation logic for Swagger 2.0 specs.

Alternative Solution with Apyhub:
Consider using Apyhub's API Converter, which handles Swagger 2.0, OpenAPI 3.x, and other formats without manual modifications. Example usage:

`const apyhub = require("apyhub");

async function convertSpec() {
const data = {
file: await apyhub.prepareFile("swagger.json"),
output_format: "postman"
};

const response = await apyhub.convert("specification", data);
console.log(response);
}

convertSpec();`