Current name is used as a "reference" name to refer to that particular scheme in OpenAPI spec (in yaml or json it is key value of the map containing security schemas)
But spec refers to name as a field in that object with very specific semantic
The name of the header, query or cookie parameter to be used.
After this change name will become what it is supposed to be - name of query/header/cookie, and for "reference" name there is a new required field.
This change will break those, who uses name as "reference" name, but it will bring library closer to OpenAPI spec.
Fixes https://github.com/papsign/Ktor-OpenAPI-Generator/issues/114
BREAKING CHANGE
Current
name
is used as a "reference" name to refer to that particular scheme in OpenAPI spec (in yaml or json it is key value of the map containing security schemas)But spec refers to
name
as a field in that object with very specific semanticThe name of the header, query or cookie parameter to be used.
After this change
name
will become what it is supposed to be - name of query/header/cookie, and for "reference" name there is a new required field.This change will break those, who uses name as "reference" name, but it will bring library closer to OpenAPI spec.