Allow setting HTTP headers per request about sailor HOT 4 CLOSED

Can you provide details for an actual use case where headers must be set per request?

from sailor.

I would like to avoid adding additional arguments to the generated Operation::execute() method, since that could clash with the generated arguments. We could use something like a builder pattern:

MyQuery
    ::withOptions(['headers' => ...])
    ->execute(1, 'asdf');

The actual client implementation is decoupled by an interface though, which currently only requires a single request() method. I wonder how we would extend that, can we have a one-size-fits-all implementation? Do we need to restructure that completely?

from sailor.

Yeah i had a play with adding arguments to Operation::execute() and it got complex real quick. The builder option looks like it could be a nice though, will have a play with that

We use headers for a few things, adding context about the user so that infrastructure can route things, but the main pain point is that we call a downstream graphql endpoint as the user that is logged in an set the authorization header to be the users token

from sailor.

https://github.com/spawnia/sailor/releases/tag/v0.10.0 solves this.

Dynamic clients

You can configure clients dynamically for specific operations or per request:

/** @var \Spawnia\Sailor\Client $client Somehow instantiated dynamically */
\Example\Api\HelloSailor::setClient($client);

// Will use $client over the client from EndpointConfig
$result = HelloSailor::execute();

// Reverts to using the client from EndpointConfig
HelloSailor::setClient(null);

from sailor.