Leslie Fung

> ```ts > interface Generic { > genericProp: T; > } > > type A = Generic > ``` > Off the top of my head: > 1. Parse type...

We currently don't have support for generating `cookie` params as defined by the OpenAPI's [Parameter Locations](https://swagger.io/specification/#parameter-locations). However there is support for optional `@headers`: ```ts @request request( @headers headers: { Accept:...

> It could be, thanks @lfportal. > > I am wondering if you could elaborate on the `security-header` part of the specification. Can this be used to globally specify the...

Spot should be cater for examples at any point where a type is defined or referenced. Asides from the existing `header`/`path`/`query` params, the following elements refer to types: `body`, `interface...

> Hi @lfportal , since this is currently unassigned can I take this up ? @mahirk is this one you're currently actively tackling?

@san-gh are you happy to pick this one up?

Hi @jankuca I think your suggestion makes sense. What do you think of: ```ts @request({ contentType: 'multipart/form-data' // defaults to application/json }) req(...) {} @response({ status: 200, contentType: 'multipart/form-data' //...

> Yes, you are basically quoting my proposal: > > > or more explicit `{ contentType: 'multipart/form-data' }` > > Being able to specify different bodies based on the `contentType`...

@hffmnn a bug was introduced as part of a migration that caused interface descriptions to not be parsed. This has been fixed in `v1.0.2`. Basic JsDoc descriptions are used to...

Hi @estahn, just to clarify are you after the ability to set the media type globally? (i.e. change all `application/json` to `application/vnd.api+json`) Or are you after the ability to set...