breaux
Contributor
Joined 12 years ago
User Profile
User Widgets
Contributions
Re: Documentation Export with inherited types is incorrect
So I can't export HTML and get a flat display of the types? That would make me quit using hierarchical types. I don't want viewers of my HTML exports to have to be exposed to that confusing syntax 😞 (Just to be clear, I'm not talking about the pretty formatting/display, but about the exposure of the internal type hierarchy with each method.)Documentation Export with inherited types is incorrect
I have an openapi: 3.0.0 API where I've used type inheritance for some requests & responses, and when I view those in the SwaggerHub editor or viewer, they look as I want/expect: all the fields collapsed into a flat object: But when I export the file to HTML, I instead get a very confusing view of all the nested "all of" elements. How can I get the exported documentation to look like the online documentation in this regard?Re: REST, MockAction, using template parameters in ResourcePath
Sounds like you actually have to script a mock request at the highest level of the REST resource hierarchy :-( https://stackoverflow.com/a/37343814/796761 Which is a major pain. Because our API's REST resources are subpaths of each other, and you can't use template parameters or wildcards in mock patterns. So I'd have to script the entire base path or create all kinds of duplicates with hardcoded values, in order to distinguish, say, /calendar-backend/public/api/v1/services from /calendar-backend/public/api/v1/services/1/branches from /calendar-backend/public/api/v1/services/2/branches
