菜单
Use when making HTTP calls that should return Result<T> instead of throwing exceptions — GetFromJsonResultAsync, PostAsJsonResultAsync, DeleteResultAsync on HttpClient, and HttpRequestBuilder for fluent multi-header/query-param requests with optional Polly resilience.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when representing optional values explicitly — Maybe<T> as a null-safe container, Maybe.From()/FromTry() for creation, HasValue/HasNoValue, Map/Bind chaining, TapNone for None-side effects, Match for consumption, and ToMaybeResult() to bridge into the Result pattern.
Use when handling operation outcomes without exceptions — Result and Result<T> for success/failure, railway-oriented chaining with Then/ThenAsync/Ensure, Match for consumption, and Result.And/Or for combining multiple results.
Use when composing business validation logic — define rules as classes, Func fields, or inline lambdas; combine with .And()/.Or()/.Linear()/.Next(); evaluate with RuleEngine.Evaluate(); branch with RuleEngine.If().
Use when modeling partial success — These<TError, TValue> holds Left (error only), Right (value only), or Both (error + value), enabling scenarios where a result can partially succeed while carrying warnings. Use FromResult to bridge from Result<T>, ToResult/ToResultLenient to bridge back, and Partition to split collections.
Use when you need testable time — IDateTimeProvider wraps clock access so production code uses DateTimeProvider while tests use the built-in FakeDateTimeProvider to freeze/advance/set the clock; also provides .ToDateOnly() and .ToTimeOnly() DateTime extension methods.
Use when adding cross-cutting pipeline behaviors to CQRS handlers — ValidationBehavior (CSharpEssentials.Validation, throws EnhancedValidationException), LoggingBehavior (ILoggableRequest), ExceptionHandlingBehavior (auto-converts exceptions to Result.Failure for Result-returning handlers), CachingBehavior (ICacheable with IDistributedCache), and TransactionScopeBehavior (ITransactionalRequest).
| name | csharpessentials-http |
| description | Use when making HTTP calls that should return Result<T> instead of throwing exceptions — GetFromJsonResultAsync, PostAsJsonResultAsync, DeleteResultAsync on HttpClient, and HttpRequestBuilder for fluent multi-header/query-param requests with optional Polly resilience. |
HttpClient extensions that return Result<T> instead of throwing on 4xx/5xx. Never catch HttpRequestException again.
dotnet add package CSharpEssentials.Http
using CSharpEssentials.Http;
// Register typed client
builder.Services.AddHttpClient<UserApiClient>(c =>
c.BaseAddress = new Uri("https://api.example.com"));
// GET
Result<User> result = await _client.GetFromJsonResultAsync<User>("/users/1");
// POST
Result<Order> posted = await _client.PostAsJsonResultAsync<Order>("/orders", newOrder);
// PUT
Result<User> updated = await _client.PutAsJsonResultAsync<User>("/users/1", userDto);
// DELETE
Result deleted = await _client.DeleteResultAsync("/orders/1");
// All methods: 2xx → Success, 4xx/5xx → Failure with Error describing the HTTP status
var result = await new HttpRequestBuilder(_client)
.WithUrl("/search")
.WithQueryParam("q", query)
.WithQueryParam("page", "1")
.WithHeader("X-Api-Key", apiKey)
.WithHeader("X-Correlation-Id", correlationId)
.GetAsync<SearchResult>();
builder.Services.AddHttpClient<ApiClient>()
.AddRetryPolicy(retryCount: 3)
.AddCircuitBreakerPolicy(
handledEventsAllowedBeforeBreaking: 5,
durationOfBreak: TimeSpan.FromSeconds(30));
HttpRequestBuilder over raw HttpClient for multi-header or multi-param requestsResult.ThenAsync() to chain downstream calls without nested try/catchHttpClient classes rather than IHttpClientFactory directly for testability