Structural improvements: move root externalDocs to info
This issue is quite simple it's only about moving the root externalDocs into the info object to simplify root.
before:
info:
# (existing) info object
externalDocs:
# link to some external documentation about the API
after:
info:
# (existing) info object + externalDocs
(... same properties as existing info object)
externalDocs:
# (existing) Moving externalDocs from root to info
I'm not sure I see the benefits. Yes the root has one less property, but now the info object has one more. What is the benefit of having less properties in the root?
I don't feel strongly one way or the other, but if we are going to make a breaking change then I think we should have a fairly good justification.
Having now read OAI/sig-moonwalk#115 I see the reason for your proposal.
parent OAI/OpenAPI-Specification#560
Closing this as included in
- OAI/sig-moonwalk#116
as it would be part of a major version change to remove/move a top-level field.