I'm trying to use swagger-js
to generate client code for a service that requires manual download of its spec. That is, the service publishes its spec, but its not downloadable in an automated way.
I've got the spec on the filesystem, but the problem is that swagger-js
, which depends on isomorphic-fetch
, which in turn depends on node-fetch
, doesn't support file://
urls or absolute filesystem paths.
Relevant issues are https://github.com/swagger-api/swagger-js/issues/1044, https://github.com/matthew-andrews/isomorphic-fetch/issues/76 & https://github.com/bitinn/node-fetch/issues/75.
Is there a workaround for this scenario until these issues are resolved?
via Matthew Adams
No comments:
Post a Comment