Skip to content
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 issue with operationId #93

Open
ghost opened this issue Sep 5, 2018 · 4 comments
Open

OpenAPI 3 issue with operationId #93

ghost opened this issue Sep 5, 2018 · 4 comments

Comments

@ghost
Copy link

ghost commented Sep 5, 2018

We have encountered an issue while using an OpenAPI 3 specification.

Error: Operation 'getContractVersionDocument' does not have an operationId or summary member.

In our spec, the operationId is what is being returned as getContractVersionDocument so I am very confused as to why this issue is being raised. How come it needs a summary if it already knows the operationId.

I have tried to follow this through the code, sadly I don't code in go and have got very lost.

@ghost
Copy link
Author

ghost commented Sep 5, 2018

I have tested this with the Petstore example in OpenAPI v3 and it fails with the same error.

It looks to me like the binary download of this project doesn't support v3 of the spec :/

@erans
Copy link

erans commented Dec 4, 2018

As far as I can see issue #63 is still open which means DapperDox at the moment doesn't support OpenAPI 3.0

@tadeoos
Copy link

tadeoos commented Jul 24, 2019

I see the same error when using OpenAPI 2 specification (I'm on macOS)

The operationId field is definietly there but I don't have summaries.

@Abhishek-Bajpai
Copy link

I am running into the same issue with "swagger":"2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants