Swagger-editor: should NOT have additional properties additionalProperty: components

[chorsnell]

Using the example under 'Common Parameters for Various Paths' - https://swagger.io/docs/specification/describing-parameters/

Schema error should NOT have additional properties
additionalProperty: components
Jump to line 0

This is on https://editor.swagger.io/ so I presume latest version?

[webron]

Are you defining a Swagger 2.0 or OpenAPI 3.0.0?

[hkosova]

@poppahorse that doc is for OpenAPI 3.0.0. If you use OpenAPI/Swagger 2.0, check out https://swagger.io/docs/specification/2-0/describing-parameters/

[shockey]

Closing due to inactivity.

This is simply to keep our issue tracker clean - feel free to comment if there are any further thoughts or concerns, and we'll be happy to reopen this issue.

[Diarsid]

Hi all. We have this issue and we cannot get it solved. Googling didn't help.

We're developing a Java rest service using Spring MVC and we have following endpoint:

@ApiOperation(value = "Get doc for entity by specified UUID")
@GetMapping("{uuid}/doc")
public ResponseEntity<?> getEntityDoc(
                  @PathVariable UUID uuid,
                  @RequestParam Map<String, String> queryParams,
                  @RequestParam UUID token) {

Swagger editor shows this endpoint description properly, but reports error:

chema error at paths['/entities/{uuid}/doc'].get.parameters[1]
should NOT have additional properties
additionalProperty: items, name, in, description, required
Jump to line 1630

Schema error at paths['/entities/{uuid}/doc'].get.parameters[1].in
should be equal to one of the allowed values
allowedValues: body, header, formData, path
Jump to line 1631

Schema error at paths['/entities/{uuid}/doc'].get.parameters[1].items
should NOT have additional properties
additionalProperty: additionalProperties
Jump to line 1634

Schema error at paths['/entities/{uuid}/doc'].get.parameters[1].items.type
should be equal to one of the allowed values
allowedValues: string, number, integer, boolean, array
Jump to line 1635

[webron]

@Diarsid it's impossible to help without having a full API definition. Please file a new ticket and follow the issue template.

[tonystaark]

Hmm is it better for beginners or new learners to pick up or use Swagger 2.0 or OpenAPI 3.0.0 nowadays?

[shockey]

@tonystaark I'd recommend 3.0 — 2.0 is no longer being updated by the OpenAPI Initiative, and will only age further.

---

Locking this, as it is very old and resolved.