Version 0.0.4 #8
Merged
+86
−114
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduced HttpResponseException in MediatR.MinimalApi.Exceptions for improved error handling, allowing exceptions to carry HTTP status codes. Enhanced GetUserByIdQueryHandler to throw HttpResponseException with a 400 status code for empty UserId, ensuring meaningful HTTP responses for invalid requests. Refactored MediatREndpoints with new methods for error handling, including specific handling for HttpResponseException and general exceptions, facilitating clearer and more informative responses to clients. Updated namespace imports in affected files to support these changes.
This commit introduces a new attribute, `EndpointFilterAttribute<T>`, in the `MediatR.MinimalApi.Attributes` namespace, designed to associate filters with endpoint handlers for pre-processing or post-processing requests. The `MediatREndpoints` class has been enhanced to support this new functionality by adding filters to routes based on the attributes applied to handler types. Additionally, a new `EndpointFilterExtensions` class provides an extension method `AddFiltersFromAttributes` for `RouteHandlerBuilder`, enabling the dynamic addition of filters by resolving filter instances from the service provider and applying them to the route handler builder. These changes collectively establish a mechanism for declaratively applying filters to endpoint handlers in a minimal API setup using MediatR.
…ass in `MediatR.MinimalApi.Extensions` for mapping HTTP methods to MediatR requests.
…suring that the `context.RequestAborted` cancellation token is passed both when sending requests through MediatR
…r the main branch
…r the main branch
- Implemented a try-catch block in `MapMethodWithMediatR<TRequest, TResponse>` for graceful error handling, catching `HttpResponseException` and returning appropriate HTTP responses.
…nctionality of the role management endpoints, ensuring they work as intended.
- Updated target framework from .NET 8.0 to .NET 9.0. - Upgraded `FluentValidation` and `FluentValidation.DependencyInjectionExtensions` to 11.11.0. - Upgraded `Microsoft.AspNetCore.Authentication.JwtBearer` and `Microsoft.AspNetCore.OpenApi` to 9.0.0. - Replaced `Swashbuckle.AspNetCore` with `Scalar.AspNetCore` 1.2.74. - Replaced `Swagger` setup with `OpenApi` setup in `Program.cs`. - Added `BearerSecuritySchemeTransformer` for OpenAPI Bearer security. - Changed `launchUrl` in `launchSettings.json` to "scalar/v1". - Simplified `ValidationBehavior` by removing `BuildErrorMessage` method. - Updated `MediatR.MinimalApi` to target .NET 8.0 and .NET 9.0, version 0.0.4. - Updated `MediatR.MinimalApi.Tests.Integration` and `MediatR.MinimalApi.Tests.Unit` to target .NET 9.0.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.