Create types from URL about openapi-typescript HOT 4 CLOSED

@psmyrdek a PR for that would be greatly appreciated!

What about if we just skipped the --url flag altogether, and just accepted it as the main input?

npx @manifoldco/swagger-to-js https://remote.com/specs.json …

And we’d just parse that first param: if it starts with a remote protocol fetch it; otherwise assume it’s a local file. I think that’d keep the API simpler. And it’d save us from having to conditionally require that first param or not.

It’s not exactly outlined, but a goal of this project is to keep dependencies as few as possible for performance. So if we could get away with using Node’s core http/https modules for fetching that’d be ideal.

from openapi-typescript.

It will be useful for me too. Also I shouldn't write it here, but I also want to enum type to be parsed properly.
Upd: Oh.. I found this issue too=)

from openapi-typescript.

Also I shouldn't write it here, but I also want to enum type to be parsed properly.

@RinatGumarov You sure shouldn’t write a different issue in an unrelated ticket! 😛 Feel free to open another issue with a reproduction of your issue and the version you’re using please 🙇

from openapi-typescript.

@DangoDev Sounds good - will prepare a PR as quickly as I can.

from openapi-typescript.