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.
26 lines
711 B
C#
26 lines
711 B
C#
using ErrorOr;
|
|
using Mediator;
|
|
using Musify.Application.Users.Responses;
|
|
using Musify.Domain.Entities;
|
|
|
|
namespace Musify.Application.Users.Commands
|
|
{
|
|
public record CreateUserCommand(long Id,
|
|
string Name,
|
|
string? FirstName,
|
|
string? SecondName)
|
|
: ICommand<ErrorOr<UserApplicationResponse>>
|
|
{
|
|
public static User ToEntity(CreateUserCommand command)
|
|
{
|
|
return new User
|
|
{
|
|
Id = command.Id,
|
|
Name = command.Name,
|
|
NormalizedName = command.Name.ToUpperInvariant(),
|
|
FirstName = command.FirstName,
|
|
SecondName = command.SecondName
|
|
};
|
|
}
|
|
}
|
|
} |