From 7ddfe67b9bb2c32d8417fb0cf540679faa973e83 Mon Sep 17 00:00:00 2001 From: Tom Brereton Date: Tue, 3 Dec 2024 11:11:02 +1100 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a65a335..d83ecac 100644 --- a/README.md +++ b/README.md @@ -43,7 +43,7 @@ I want to have a starter template for building Dotnet Apis. Things that are impo ## Architectural Decision Records - Have a thin endpoint/controller and move the logic into a handler/service class so it's (1) unit testable and (2) decoupled from the endpoint framework to ease with refactoring e.g. moving the handler to a `Core` or `Application` project. -- (Exploring) Use Result objects for control flow instead of exceptions. In common code paths like validation or business rules use Result.Failure() or Result.Success(); use Exceptions for situations like failed connection, out of memory, access array incorrectly +- (Exploring) Use [Result]([url](https://www.milanjovanovic.tech/blog/functional-error-handling-in-dotnet-with-the-result-pattern)) objects for control flow instead of exceptions. In common code paths like validation or business rules use Result.Failure() or Result.Success(); use Exceptions for situations like failed connection, out of memory, access array incorrectly ## Prerequisites