LMB.FluentHttpClient
1.0.1
This is an HTTP client that can be used to consume HTTP APIs and was developed using the Fluent Interface design pattern.
Install-Package LMB.FluentHttpClient -Version 1.0.1
dotnet add package LMB.FluentHttpClient --version 1.0.1
<PackageReference Include="LMB.FluentHttpClient" Version="1.0.1" />
paket add LMB.FluentHttpClient --version 1.0.1
Fluent Http Client
This is an HTTP client that can be used to consume HTTP APIs and was developed using the Fluent Interface design pattern.
First, by using this pattern we make the code more readable, and easy to understand.
This makes it easier to make changes later on.
Second, the Fluent Interface can be used to force the programmer to perform certain steps before they perform others.
An object can have a method that uses data it expects to have been set in another method.
How it works?
Using the power of interfaces, we can enforce “rules of grammar”, and make it that certain methods cannot be called, until all the required setup methods have been called.
Whe achieve that, by following these three steps to create the fluent interface:
- Define all possible combinations of the natural language syntax.
- Create the interfaces that enforce the grammar rules.
- Build the class, implementing the interfaces.
Other important thing to consider here is that, when we are defining the syntax, we have different types of methods:
Initiating/Instantiating
These are the methods we use to start the call.
Chaining/Continuing
These are the methods we call in the middle of the statement, and that let us call another method after them.
When any of these methods are called, you can keep on calling other methods. That’s known as “method chaining”.
Executing/Ending
These are the methods that finally do some action, and end our statement.
Full Documentation
For a full documentation please see the GitHub repo
Fluent Http Client
This is an HTTP client that can be used to consume HTTP APIs and was developed using the Fluent Interface design pattern.
First, by using this pattern we make the code more readable, and easy to understand.
This makes it easier to make changes later on.
Second, the Fluent Interface can be used to force the programmer to perform certain steps before they perform others.
An object can have a method that uses data it expects to have been set in another method.
How it works?
Using the power of interfaces, we can enforce “rules of grammar”, and make it that certain methods cannot be called, until all the required setup methods have been called.
Whe achieve that, by following these three steps to create the fluent interface:
- Define all possible combinations of the natural language syntax.
- Create the interfaces that enforce the grammar rules.
- Build the class, implementing the interfaces.
Other important thing to consider here is that, when we are defining the syntax, we have different types of methods:
Initiating/Instantiating
These are the methods we use to start the call.
Chaining/Continuing
These are the methods we call in the middle of the statement, and that let us call another method after them.
When any of these methods are called, you can keep on calling other methods. That’s known as “method chaining”.
Executing/Ending
These are the methods that finally do some action, and end our statement.
Full Documentation
For a full documentation please see the GitHub repo
Release Notes
Added the dependencies for the packages:
Microsoft.AspNet.WebApi.Client
Newtonsoft.Json
Dependencies
-
.NETStandard 2.0
- LMB.GenericEntityBase (>= 1.1.0)
- Microsoft.AspNet.WebApi.Client (>= 5.2.3)
- Microsoft.AspNetCore.Mvc.WebApiCompatShim (>= 2.0.0)
- Newtonsoft.Json (>= 10.0.3)
GitHub Usage
This package is not used by any popular GitHub repositories.
