Stanislav Molchanovskiy

Cloner class

5

This class will allow users not to write wrappers to make their code more testable and flexible.

Using Activity for requests

2

This allows to collect more telemetry about the request for monitoring and investigation of problems. This will be helpful for usage of NClient, as well as for the development and...

Named client

1

A named client will allow you to use named options when creating via DI: ```C# services.Configure(name: "myClient", options => { options.JsonSerializerOptions.PropertyNameCaseInsensitive = true; }); services.AddNClient(name: "myClient", host: "http://localhost:5001"); // Use...

Client-side service discovery

3

I would like to be able to implement [the client-side service discovery pattern](https://microservices.io/patterns/client-side-discovery.html).

Creating custom providers using DI

2

I want to create custom providers using DI. From the client's API side, it should look like this: ```C# services.AddRestNClient(host: "http://localhost:5000", implementationFactory: builder => builder .WithHandling() .Build()); ```

Currently, the method is able to work with tokens. But I would like to be able to pass ICredentials there, for example, for Kerberos authentication

Support capturing diagnostics information using DiagnosticSource

6

DiagnosticSource is a tool that will allow client users to subscribe to events and use them to log and send metrics. As an example, we can take the [Elastic client](https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/diagnostic-source.html)....

Support for default interface methods

1

WIP

Sometimes it becomes necessary to send additional requests in the handler, for example, to process 4** response codes. Here is an [example](https://stackoverflow.com/questions/49304326/refresh-token-using-static-httpclient) of how it can be used in the...

WIP