Read "consumes" and write into "headers" about swaxios HOT 6 CLOSED

Hmm. I haven't thought of that case. If we don't set the 'content-type', then axios will automatically assign one. I think we should stay with this implementation until it becomes a problem.

from swaxios.

I think axios supports XML too so we should be good with it's auto detection mode for now. I would close this issue until it becomes a problem. WDYT?

from swaxios.

@bennyn What if consumes contains multiple entries?

Example:

  "/api/v1/exchange/{id}": {
    "delete": {
      "consumes": [
        "application/json",
        "application/xml"
      ],
      // ...
  }

from swaxios.

We could use this idea to filter out paths which only consume "application/xml" since Swaxios can't handle these anyway.

from swaxios.

Sounds good!

from swaxios.

Btw, we should probably change the return type of an endpoint which returns XML to "string".

from swaxios.