Fix not handling header/cookie params

[slikts]

Skips header/cookie params, since they would normally be set globally instead of per-request, although I'm not sure if this is the correct approach, and it just fixes my usecase. Additionally, since the header names were not normalized, it would produce invalid syntax like this: getPet: (petId?: string, X-Example?: string).

[rametta]

Hey @slikts, thanks for the PR!

The invalid syntax for headers is definitely a bug that needs fixing, I agree.

Removing the headers from the query is an interesting situation though - I don't think we can assume all headers should be set globally because there are definite use-cases where people would need to set headers per request.

I think we should opt for the most flexible approach first (per request) and then see if there's maybe a way to specify inside the yaml file if it should be included globally or not. It's not a great solution either though, I will look into alternative approaches too.

[slikts]

After a bit of thought, just skipping the params really isn't correct, and the solution would be to handle cookie and header params the same way as query params are handled currently and add them to the Axios request config, and then users can just use partial application to make hooks that only take query and path params.

[rametta]

Very true. I will close this for now. Please open a PR or an issue in the future to track this if you're interested. If there's enough people asking for it, I'm sure we can figure out a nice solution