-
Notifications
You must be signed in to change notification settings - Fork 20
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
Could you add formParam back in open api 3.0 #72
Comments
Hey, it was removed because it didnt look like it was supported anymore. If
you can show me what it is called in the OpenAPI specification, I can try
adding it back. Thanks!
…On Sun, Jun 6, 2021 at 11:31 PM chenghsienwen ***@***.***> wrote:
Hi, jakehschwartz:
traced this commit that formParam have been removed
50dc183
<50dc183>
how can we add it back?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#72>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVAOZ2USSGEOV2MXISXQIDTRQ4QNANCNFSM46GXVPQQ>
.
|
I tried to add it at chenghsienwen@6f062d2 according to swagger spec however, I tried to run examples but no formParam field found
|
@chenghsienwen Do you need to register the schema, like in the bodyParam function thats above yours? |
@jakehschwartz thanks for remind, I have tried to register formParam in FinatraSwagger.scala, but it not works, I think form related field should declare in body request with finatra annotation, and bodyParam in FinatraOperation.scala should handle multipart/form-data related content type |
Hi, jakehschwartz:
traced this commit that formParam have been removed
50dc183
how can we add it back?
The text was updated successfully, but these errors were encountered: