✨ Add in exception processor for strongly typed SQL exeptions #440
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#408
This pull request focuses on enhancing the handling of SQL Server exceptions in the project. The primary goal is to produce more useful and strongly typed exceptions, improving the debugging experience and error handling.
Improvements to SQL Server exception handling:
docs/adr/20241118-produce-useful-sql-server-exceptions.md
: Added a new architectural decision record (ADR) to document the decision to use strongly typed SQL Server exceptions.src/Infrastructure/DependencyInjection.cs
: Imported theEntityFramework.Exceptions.SqlServer
package and updated theAddInfrastructure
method to use the exception processor for better exception handling. [1] [2]src/Infrastructure/Infrastructure.csproj
: Added a new package reference forEntityFrameworkCore.Exceptions.SqlServer
to the project file.No