refactor: replace Ardalis.Result with ErrorOr across the app

Ardalis Result<T> carried incoherent success sub-statuses and a clunky
generic converter; ErrorOr models success-or-errors cleanly.

- Application: all commands/queries/handlers now return ErrorOr<T>
  (non-generic Result -> ErrorOr<Success>); errors via Error.NotFound/
  Conflict/Validation/Unauthorized/Failure; success via value or new Success()
- Drop ResultExtensions.As<>(): error propagation is now just return .Errors
- Rewrite HTTP mapping (ErrorOrHttpExtensions) off Error.Type; success maps
  to 200 (value) or 204 (Success); Created still built in the endpoints
- Endpoints/gateway middleware: !IsSuccess -> IsError
- Swap Ardalis.Result package for ErrorOr 2.1.1 (remove unused ref from Worker)

Build: 0 warnings, 0 errors.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

This commit is contained in:

Admin

2026-07-05 04:05:43 +02:00

co-authored by

Claude Opus 4.8

parent a3bf796f17

commit 6e469dbb4a

56 changed files with 259 additions and 283 deletions

									
										backend/Musify.Worker/Musify.Worker.csproj
									
		-1
	
												View File
												
				@@ -5,7 +5,6 @@

				  </PropertyGroup>

				  <ItemGroup>

				    <PackageReference Include="Ardalis.Result" />

				    <PackageReference Include="AWSSDK.S3" />

				    <PackageReference Include="DispatchR.Mediator" />

				    <PackageReference Include="MassTransit" />