You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4e65476
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: AGENTS.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,7 @@ If I tell you to remember something, you do the same, update
12
12
- A successful `Result<T>` must always carry a non-null `Value`, matching its `MemberNotNullWhen` annotations. Reject null success payloads at the owning result setter/factory, including nullable type arguments and initializer overrides. Use non-generic `Result.Succeed()` for a success without a payload; never preserve a successful null value to accommodate a consumer null guard.
13
13
- Communication Orleans integration uses native generated Orleans serialization and its typed surrogates only. Do not add Newtonsoft.Json, JSON grain-storage adapters/converters, or automatic JSON storage registrations. Applications own their storage-provider serialization.
14
14
- For failure logging, use Warning with failure details when there is no exception, and Error with the original stack trace when an exception is supplied.
15
+
- Creator-approved HTTP diagnostic exception (2026-10-15): native HTTP resilience operations, HTTP-to-Result converters and HTTP CQRS readers log and trace only safe status, exception types, throw-site stacks and correlation. Exclude exception/inner messages, request/response content, reason phrases and URI user information/path/query. Preserve original transport exceptions, raw responses and exception-based retry decisions. General command/Result logging retains its original exception-object contract; HTTP privacy also applies when tracing is disabled or unsampled.
15
16
- For automatic Result failure telemetry, record the error and original exception immediately in the failure/catch path; never retain an exception reference in Result or Problem for later diagnostics.
16
17
always check all test are passed.
17
18
- Use TUnit with Microsoft.Testing.Platform for all .NET tests; do not add or retain xUnit packages, attributes, fixtures, configuration, or documentation.
0 commit comments