Expose mappersmith's full capabilities

[erikengervall]

The original discussion was spawned in #20.

The question is whether or not to expose more of mappersmith's internal capabilities to allow users to leverage its features.

Pros

• Users get access to the full list of capabilities offered by mappersmith, primarily middlewares

Cons

• It would lock v1.x.x to mappersmith and a change in http client would require a major version bump

[khajvahmac]

Bumping this thread. Are there any updates regarding this? Our use case is, we need to pass a authorization header. Custom middleware would do the trick but there is the exposure of mappersmith's middleware API which I think is a bit of overkill, as there shouldn't be too much need for request manipulation.

Maybe we can have a custom headers support? That should cover most of the authentication needs and not expose implementation detail.

[mbuotidem]

@erikengervall Do you know if there's a plan to implement this? I have the same use case as @khajvahmac and its also come up in #239. @khajvahmac did you find a workaround for this you could share?

[toanvc]

@mbuotidem hello I created a PR here #249 for the workaround in our project.