re: Defining reusable components with the OpenAPI specification VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Why overload the the semantics of path and not simply add a "fragment: true" to the info object? ("x-fragment" until it is adopted in the standard)...
 

The presence of paths: {} isn't intended to overload the meaning, it's because paths is a mandatory object in the OAS (2.0 and 3.0.x), although it can be empty.

x-fragment is a good idea to make that explicit.

code of conduct - report abuse