How to access the service interface to set its property?

[ruslan-mogilevskiy]

I have an API interface with a property that acts as an HTTP header value source:
public interface IApi { [Header("X-Header")] string AuthHeader { get; set; } }

and register it with the services.AddRestEaseClient("base address").
The AuthHeader value is known on the client registration time.

Q: when calling the AddRestEaseClient how to access the IApi instance (which is generated with RestEase.For under the hood) to set its AuthHeader property value?

[netclectic]

See the 2nd example under the Using HttpClientFactory section of the readme...

https://github.com/canton7/RestEase#using-httpclientfactory

[canton7]

Good question, there's no way currently. It's not too hard to add technically, but the overloads are becoming a bit of a mess and it's hard to add extra parameters in a way which doesn't break backwards compat.

[ruslan-mogilevskiy]

Good question, there's no way currently. It's not too hard to add technically, but the overloads are becoming a bit of a mess and it's hard to add extra parameters in a way which doesn't break backwards compat.

It could be quite easily added and it will be backward compatible. I've switched to the UseWithRestEaseClient but it's also applicable to the AddRestEaseClient.

HttpClientFactoryExtensions.cs

public static IHttpClientBuilder UseWithRestEaseClient(
this IHttpClientBuilder httpClientBuilder,
Action? configurer = null,
Action? proxyConfigurer = null,
RequestModifier? requestModifier = null)
where T : class
{
return httpClientBuilder.AddRestEaseClientCore(typeof(T), GenericFactory(configurer, proxyConfigurer), requestModifier);
}

    static Func<HttpClient, object> GenericFactory<T>(Action<RestClient> configurer, **Action<T> proxyConfigurer**) where T : class
    {
        return httpClient =>
        {
            var restClient = new RestClient(httpClient);
            configurer?.Invoke(restClient);
            var proxy = restClient.For<T>();
            **proxyConfigurer?.Invoke(proxy);**
            return proxy;
        };
    }

• sorry for the formatting, it's tricky to make proper code formatting on GitHub.

[canton7]

Right, but that change you made is a binary break -- people compiled against the old version of that method signature will now fail at runtime. I ended up taking this approach: f80748c

[canton7]

I'll try and release that tomorrow

[ruslan-mogilevskiy]

Currently, I've fixed this problem by adding the header explicitly in the standard ConfigureHttpClient() but smashes the API interface setup across the application (API methods are in the IApi interface while its auth headers are outside of it).

[canton7]

Released as 1.6.0