Darrel
@iambingoNJU No. Version 3.0 of the spec still only uses the path portion of the resource identifier to identify operations.
No. It is one of the topics under consideration for the next version https://github.com/OAI/OpenAPI-Specification/issues/2572
@webron Can you get an authoritative opinion on this?
I think I would be tempted to point to single HTML file that had links to other docs from there. I think if we start trying to describe different kinds...
This was not an oversight. It is an intentional design choice based on years of conversations on how to resolve the semantics of merging one or more objects together. JSON...
@njr-11 How this headers are actually rendered is a function of the tool you are using, not the specification. I would suggest bringing this up with whatever tooling you are...
We were a bit stuck when allowing the `deepObject` style. We understood that users wanted this capability but there is no standard definition of what that serialization format looks like....
@benhaynes Sorry if this comes across as snarky, it's not intended to, it's just I'm in a rush and I don't know how to ask this in a friendly/sincere way....
Does someone have a proposal of how we can fix the OpenAPI specification to allow it to tell tooling which flavour of deepNesting object serialization to use? If someone wants...
Thanks everyone for the input here. This is exactly the type of information we needed, but didn't have when were originally defining the deepObject style. I am a little concerned...