Sg set headers

[badaz]

Possibility to add headers on a client's scope (up to now it was only possible by passing a param object to authorizedFetch, and not possible to pass it to methods like find, create, etc... in clients)

[jdeniau]

I'm not really fan of setting the headers that will impact the all call of the repository instance.

One solution that may be better is to use a wither that will return a new instance of the Repository:

class AbstractClient {
  withHeaders(headers = {}) {
    const repository = cloneTheCurrentRepository(this);
    repository.headers = headers;

    return repository;
  }
}

but this is kind of hacky too.

An even better solution may be to refactor all the queryParam = {}, pathParameters = {} parameters to pass an object containing request-dependent variables, but it is more complicated to implement.
Maybe a "dirty" solution could be to add a last parameters headers = {} after those two to keep the same logic.

What do you think ?

[badaz]

I proposed a "dirty" solution already, dictated by lazyness I must admit, but if you prefer your "dirty" solution (aka adding a headers param) then I'll go for it ^^, just have to add the param everywhere. I do not think the wither is a lot better since there is no guarantee that one does not just declare client.headers = { someHeader: "foo" }. And a unique object with request dependent params would be breaking so I'll pass. What do YOU think ?

[jdeniau]

Let's go for adding another parameter everywhere then, it would be much simpler to refactor this in a single object and the breaking changes will be easier to fix then.

I've opened #78 as a reminder