You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched existing issues to ensure a similar issue has not already been created
Description
I use Mockaco. AspNetCore in my asp.net core project,
There is already a middleware defined to handle global exceptions in my project, and there is no way to remove ErrorHandlingMiddleware when I use the UseMockaco() extension method.
Because ErrorHandlingMiddleware ,RequestMatchingMiddleware,ResponseDelayMiddleware,ResponseMockingMiddleware, CallbackMiddleware them access-modifiers is internal,
Can we make these access-modifiers of public so that we can selectively add them?
Proposed solution
Will ErrorHandlingMiddlewareRequestMatchingMiddlewareResponseDelayMiddlewareResponseMockingMiddlewareCallbackMiddleware changes their access-modifiers to public
Alternatives
Add an option to MockacoOptions to indicate whether ErrorHandlingMiddleware needs to be enabled
Additional context
No response
The text was updated successfully, but these errors were encountered:
Prerequisites
Description
I use Mockaco. AspNetCore in my asp.net core project,
There is already a middleware defined to handle global exceptions in my project, and there is no way to remove ErrorHandlingMiddleware when I use the UseMockaco() extension method.
Because ErrorHandlingMiddleware ,RequestMatchingMiddleware,ResponseDelayMiddleware,ResponseMockingMiddleware, CallbackMiddleware them access-modifiers is internal,
Can we make these access-modifiers of public so that we can selectively add them?
Proposed solution
Will
ErrorHandlingMiddleware
RequestMatchingMiddleware
ResponseDelayMiddleware
ResponseMockingMiddleware
CallbackMiddleware
changes their access-modifiers to publicAlternatives
Add an option to MockacoOptions to indicate whether ErrorHandlingMiddleware needs to be enabled
Additional context
No response
The text was updated successfully, but these errors were encountered: