-
-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenAPI 3.1: Header parameter as ref
not generated properly
#878
Labels
Comments
any status on this? is it even getting addressed? |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Its a bug in Swagger Validator you can try it here youself: https://apitools.dev/swagger-parser/online/ I opened a ticket: APIDevTools/swagger-parser#251 |
melloware
added
third-party
Issue is in upstream third-party library
and removed
third-party
Issue is in upstream third-party library
labels
Nov 12, 2023
Actually i see its an OpenAPI 3.1.0 thing. If you delcare yours like this it will work openapi: 3.0.3
info:
title: demo
version: '1.0'
paths:
/user:
get:
operationId: get-user
parameters:
- name: MyHeader
in: header
required: false
schema:
type: string |
melloware
changed the title
Header parameter not generated
OpenAPI 3.1: Header parameter not generated
Nov 15, 2023
It looks like it is if the Header is a REF its an issue. |
melloware
changed the title
OpenAPI 3.1: Header parameter not generated
OpenAPI 3.1: Header parameter as Nov 15, 2023
ref
not generated properly
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What are the steps to reproduce this issue?
with config file:
What happens?
Cannot find name 'MyHeaderParameter'.
this is the generated code:
…
What were you expecting to happen?
MyHeaderParameter generated
…
What versions are you using?
6.11.0 & 6.16.0
The text was updated successfully, but these errors were encountered: