Doesn't show request body params, and doesn't add a request body in the code examples.

[defcronyke]

Some of my routes have a required JSON request body. oax doesn't show which parameters are needed in the request body, rather it only shows the comment from the request body, which isn't enough information to make a successful request.

The code examples also don't show sending a request body at all, which they should show, otherwise they are showing an incorrect and incomplete request example.

And is there a way to show the code examples using the standard fetch() instead of axios and angular, which I think should be deprecated now that we have fetch?

[darosh]

Thanks. All sounds like the status in Readme is right: try out and examples are simply unfinished :(

For the json body param can you please add some screenshots comparing oax with some other tool it could give me a better hint to understand what is missing. Or can you add example to https://github.com/darosh/openapi-samples/blob/master/index.json ?

Regarding examples: yes there is a lot of missing and fetch should be there as well. I believe there are still good reasons for axios; e.g. fetch is too low level and does not report progress.

[defcronyke]

Here's a screenshot of one of my POST routes which takes a request body, only it doesn't show what needs to be in the body, which is pretty important if I am going to use the route:

It needs to show which parameters need to be in the request body, as well as their datatype, something like:

body: {
userID: 0
}

Otherwise there's no way to know how to make the request properly, we only know that we need some type of request body, it leaves us guessing.

The code examples also need to show requesting with a body, which they currently don't, only headers.

Thanks for looking into it.

[adivated]

You have to patch up the generated code to handle JSON body for all calls, it doesn't generate placeholder parameters for them. Not hard, just a little tedious. The other option would be to expose the underlying RestClient object so you could muck with it's properties directly from your own code, but I chose the former approach for simplicity.