-
Notifications
You must be signed in to change notification settings - Fork 146
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
Switch statement must have at least... #37
Comments
Hi Nitrag Reminds me that I should add a step before generating that lints the spec. |
Yea you're probably right. The API isn't complete, barely started really.
I'll check back in a bit when it's a little more developed.
…On Sat, Jul 29, 2017 at 12:16 PM, Yonas Kolb ***@***.***> wrote:
Hi Nitrag
What does your operation spec look like. It might be that your operation
spec is missing a responses field?
From the Swagger spec, each operation requires at least one defined
response https://swagger.io/specification/#responses-object-54
Does that answer your issue?
Reminds me that I should add a step before generating that lints the spec.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMBkqu9Iv8vPdH1MiOuEKibX6M9HW2Dks5sS1rggaJpZM4OnYXB>
.
|
Ok, then closing this now. Let me know if you have any other issues |
ActivateCreate.swift
The text was updated successfully, but these errors were encountered: