REslava.Result.Http 1.36.0

REslava.Result.Http

HttpClient extensions that return Result<T> instead of throwing.

Map HTTP 4xx/5xx status codes to typed domain errors and wrap network failures in ExceptionError — no try/catch, no manual status code checks.

What It Does

// Before — boilerplate repeated in every service/repository
var response = await httpClient.GetAsync($"/api/users/{id}");
if (!response.IsSuccessStatusCode)
    return Result<User>.Fail(new NotFoundError("User", id));
var user = await response.Content.ReadFromJsonAsync<User>();
return Result<User>.Ok(user!);

// After
Result<User> result = await httpClient.GetResult<User>($"/api/users/{id}");
Result<Order> posted = await httpClient.PostResult<CreateOrderDto, Order>("/api/orders", dto);
Result<Order> updated = await httpClient.PutResult<UpdateOrderDto, Order>($"/api/orders/{id}", dto);
Result deleted = await httpClient.DeleteResult($"/api/orders/{id}");

Quick Start

dotnet add package REslava.Result
dotnet add package REslava.Result.Http

using REslava.Result.Http;

// In a service/repository
public async Task<Result<User>> GetUserAsync(int id, CancellationToken ct = default)
    => await _httpClient.GetResult<User>($"/api/users/{id}", cancellationToken: ct);

public async Task<Result<User>> CreateUserAsync(CreateUserDto dto, CancellationToken ct = default)
    => await _httpClient.PostResult<CreateUserDto, User>("/api/users", dto, cancellationToken: ct);

Available Methods

All methods accept optional HttpResultOptions? and CancellationToken.

Default Error Mapping

Configuration

Customise JSON deserialization and/or the status code → error mapping:

var options = new HttpResultOptions
{
    // Custom JSON options (default: JsonSerializerDefaults.Web)
    JsonOptions = new JsonSerializerOptions
    {
        PropertyNamingPolicy = JsonNamingPolicy.SnakeCaseLower
    },

    // Custom status code mapper — completely replaces the built-in defaults
    StatusCodeMapper = (statusCode, reasonPhrase) => statusCode switch
    {
        HttpStatusCode.NotFound  => new NotFoundError("Order", requestedId),
        HttpStatusCode.Conflict  => new ConflictError("Order", "number", orderNumber),
        _ => new Error($"HTTP {(int)statusCode}: {reasonPhrase}")
    }
};

Result<Order> result = await httpClient.GetResult<Order>($"/api/orders/{id}", options);

Symmetry with Server Side

REslava.Result.Http completes the full round-trip with the server-side source generator:

SERVER (outbound): Result<T> → IResult → HTTP response  ← REslava.Result.SourceGenerators
CLIENT (inbound):  HTTP response → Result<T>            ← REslava.Result.Http

A server that returns Result<T> via [SmartEndpoint] can be consumed by a client that gets Result<T> back — no manual status-code inspection at either end.

Requires

• REslava.Result (automatically installed as a dependency)

Links

• GitHub Repository
• Changelog
• Documentation

MIT License | .NET 8 / 9 / 10