parameters from "endpoint level" are not taken into account

[Leemur89]

Hello,

Parameters can be in the OAS at both endpoint level, and method level.
For parameters at method level, they are well taken into account in data mapping. However for endpoint level, they are not being filled at all.

Example:

{
    "/my/endpoint": {
      "parameters": [
          {
            "description": "This is at endpoint level",
            "in": "header",
            "name": "endpoint-header",
            "required": true,
            "schema": {
              "type": "string"
            }
          }
      ],
      "post": {
        "parameters": [
          {
            "description": "This is at method level",
            "in": "header",
            "name": "method-specific-header",
            "required": true,
            "schema": {
              "type": "string"
            }
          }
        ],
        (...)

The library will only consider the header method-specific-header, not the endpoint-header
I'm not 100% sure that this kind of OAS is valid though :/

[robinmackaij]

I'm pretty sure it's valid in the OAS but I did not previously spend effort on supporting this. The OAS offers many options like this that generally not seen in production (since most OAS specs are generated by frameworks and not hand-crafted).

That being said, I can definitely see about supporting this if you need it (and a PR is of course welcome).