Body required params & Model about openapi-viewer HOT 3 CLOSED

would you consider to move to RapiDoc https://mrin9.github.io/RapiDoc/ ?

Currently, I am focusing on RapiDoc project, so updates to this project will be little delayed. But I plan to keep both of them in sync

If you are unable to move to RapiDoc, let me know whats the concern is, and I will see if i can resolve it.

Having said that, the issue that you mentioned was an issue in RapiDoc too, which is now fixed
Regarding your other question, to have a global schema section. I do not plan to create one for now

My main reason not to have a global schema is, in my experience, people do not use that section so much and most importantly for a larger specs that is spanned across multiple files, it becomes a performance bottleneck

But if you can provide me a compelling reason I might consider adding it

from openapi-viewer.

Hello

No , sadly I'd like to use vue.

As for the required properties I developed it. Example below (also working for nested objects of course) :

With json

"components" : { "schemas" : { "MyObject" : { "required" : [ "name", "status" ], "type" : "object", "properties" : { "name" : { "type" : "string", "example" : "Come say hi !" }, "status" : { "type" : "string", "enum" : [ "active", "inactive", "draft", "archive" ] }, "start" : { "type" : "string", "format" : "date-time" }, "end" : { "type" : "string", "format" : "date-time" } } } }
Will do the same with descriptions soonish. If it's of interest I can share. Not styled yet as it'll probably get revamped in my project.

Global schema I'll do in some custom descriptions in the page after all so no problem. Not a big fan of it myself, but it's not my decision to make.

Thanks again.

from openapi-viewer.

I am happy to accept a PR for the required properties. Once you style them and run through some really large schemas

Thanks

from openapi-viewer.