You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand its kind of silly, but sometimes it is very useful to pass complex object for GET operation, e.g. JSON Web Token(JWTs).
We can borrow the Consumer definition of Operation, in swagger spec file, if we let header parameter to refer to object type, SwaggerUI can easily show what kind of request is acceptable. Codegen can generate code accordingly. Currently header param only supports String, but we can add type definition. When come to HTTP Content-Type(MIME), we don't really care about it much. Swagger is used to demonstrate interface between client and service provider, SwaggerUI and Editor/Codegen can fill that gap. Actually body and header have no difference at all from user's perspective, just place to hold data. Many thanks.
The text was updated successfully, but these errors were encountered:
I understand its kind of silly, but sometimes it is very useful to pass complex object for GET operation, e.g. JSON Web Token(JWTs).
We can borrow the Consumer definition of Operation, in swagger spec file, if we let header parameter to refer to object type, SwaggerUI can easily show what kind of request is acceptable. Codegen can generate code accordingly. Currently header param only supports String, but we can add type definition. When come to HTTP Content-Type(MIME), we don't really care about it much. Swagger is used to demonstrate interface between client and service provider, SwaggerUI and Editor/Codegen can fill that gap. Actually body and header have no difference at all from user's perspective, just place to hold data. Many thanks.
The text was updated successfully, but these errors were encountered: