-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openapi support #3
Comments
I've had a quick look into this, and this is something I'd really like to get off the ground. It'd be nice to support a few different types of configs, support for Postman and Insomnia etc... I'm going to keep this issue open and will keep it updated with any decisions made regarding this. In the meantime if you have any further ideas about how this could work, feel free to leave comments on this issue. |
I think this could work 2 ways:
TL;DR: I think option 1 is better in the long run, but option 2 is quicker and shorter even if it's a hack |
@AdvancedHacker101 hey there, thanks for weighing in on this! I've also had a think regarding both of these options. Currently leaning towards a longterm way of implementing option 2. This is because if it is abstracted well, and we are able to transform OpenAPI -> what's there now, we'd also be able to look at supporting any other configs out there, i.e. PostMan and Insomina. I'm not trying to reinvent the wheel with a new standard as such, but the current spec has been thought out in such a way that it can be extended to do some really cool things. For example, right now we currently have a single So in short, if I am able to come up with a way for option 2 that is not a hack, that would be great. What do you think about this? |
For the other specs (PostMan, Insomnia) we would need to write a converter anyways, if we want to support them, so yeah, then option 2 is the better choice here. |
@AdvancedHacker101 yeah this is a really good point. An idea I had was to sorta just convert the PostMan, Insomnia etc... at runtime, and then simply let it run normally. So at this point, in memory, it's all represented as httpu's So something like: As of right now, there is no Do you have any thoughts regarding how the cli api / commands / options may look for the transform stuff? (What I have written above was just off the top of my head) |
it would be great to see the client natively support openapi json/yaml, so rest apis that are already documented can be accessed more easily.
The text was updated successfully, but these errors were encountered: