Skip to content

Update Documentation #38

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
scottoffen merged 1 commit into from
Nov 21, 2025
Merged

Update Documentation #38

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,18 @@ FluentHttpClient is optimized for .NET 10 and the newest .NET releases, while al
| **.NET 9** | ✔️ | |
| **.NET 10** | ✔️ | LTS |

### .NETStandard Consumers

Projects targeting **.NETStandard 2.0** or **.NETStandard 2.1** do not include `System.Text.Json` in the framework. FluentHttpClient uses `System.Text.Json` internally for its JSON extensions, but the package is not referenced transitively.

If you are building against **netstandard2.0** or **netstandard2.1**, or any TFM that does **not** ship `System.Text.Json`, you will need to add an explicit package reference with a minimum version of 6.0.10 (a higher version is always recommended):

```xml
<PackageReference Include="System.Text.Json" Version="6.0.10" />
```

Apps targeting modern TFMs (such as .NET 5 and later) already include `System.Text.Json` and do not require this step.

## A Better Way to Send HTTP Requests

FluentHttpClient is built around the way you actually write HTTP code: configure the request, send it, and handle/deserialize the response. Instead of scattering headers, query parameters, content, and deserialization across multiple calls and helper classes, you express the whole flow as a single, readable chain that sits naturally on top of `HttpClient`.
Expand Down