TypeError: Parameter 'url' must be a string, not object

[drallgood]

Hi.

i'm getting the following error, when trying to import one of our products' swagger files: JS Exception Line 7658. TypeError: Parameter 'url' must be a string, not object

I'm guessing it has something to do with the fact that this appears in the content of the JSON file: "url":{"type":"string"} (this is part of our model)

[pawsaw]

I have the same issue. Any news regarding this?

[ollydcuk]

Also getting this problem. Anyone got a resolution?

[xfoxfu]

That means your file is in format Open API 3.0, which differs from Swagger 2.0.

[goodmorningbob]

Is there any update on this issue?

I am getting the above error importing a Swagger 2 yaml file that has no 'url' parameter anywhere in it at all.

[autumnfjeld]

Also getting: "Import failed" "TypeError: Parameter 'url' must be a string, not object"

when choosing Swagger 2.0 for this file https://github.com/w3tecch/express-typescript-boilerplate/blob/develop/src/api/swagger.json

Likewise, the file does not have a "url" property.

[brtdv]

+1

[stfnhh]

Same Issue here.

[reshadf]

same issue here. Which importer should we use? Using Open API 3.0 that generates a swagger.json

[richessler]

+1 Still receiving this error

[alexbedzyk]

Same issue here.

[facetheheat]

Same issue here.

[richessler]

I was able to flub this by importing to postman format, then from postman to paw. I hope this helps you all. The Swagger to Paw is still broken.

[prometheas]

This hasn't been addressed in almost 3 years' time… it's not like Swagger / OpenAPI are some obscure format that nobody uses. Not a great look.

[dmythro]

I checked Paw to initially work with Swagger based APIs, and this is really awkward, especially Paw website saying this importer is official!

[prometheas]

For what it's worth, I heard back from the support team. They claim the Swagger 2.0 import errors will be addressed, and support for 3.0 will be added "soon", though no details whether these would be in the same release, and what sort of timing to expect:

Thanks for bringing this up to our attention - we are aware of the Swagger 2.0 issues and this is something we plan to fix… [and] we are currently preparing to bring OpenAPI 3.0 support so happily, that'll be fixed soon.

That message was from mid-August, so… hang in there, gang 🙏

[command-tab]

Today: https://twitter.com/luckymarmot/status/1304171065032278017

OpenAPI 3 is coming in a few weeks too 🙏

[osipxd]

Found workaround - convert OpenAPI 3.0 to Swagger 2.0: https://github.com/LucyBot-Inc/api-spec-converter

This issue should be linked with #39

[heksesang]

Today: https://twitter.com/luckymarmot/status/1304171065032278017

OpenAPI 3 is coming in a few weeks too 🙏

OpenAPI 3 support never materialized? I get this error when trying to import an OpenAPI 3.0.3 YAML file.

[superandrew]

same problem still present

[marceldarvas]

Using the OpenAPI 3 importer did the trick for me: https://paw.cloud/extensions/OpenAPI3Importer

[prometheas]

Using the OpenAPI 3 importer did the trick for me: https://paw.cloud/extensions/OpenAPI3Importer

Thanks for letting us know, @marceldarvas -- the context of my earlier need for this capability has since vanished, but I will see if I can remember what I was doing in Aug 2020 (I at least remember which project it was… hoping it will become obvious when I put eyes back on it 😅) and see if it now works.

[lbdl]

this is still an issue, importing Apple's App Store Connect API which lists its version as "openapi" : "3.0.1" still breaks with the following: JS Exception Line (null). TypeError: Parameter 'url' must be a string, not object

Any fixes? Seems like basic functionality