-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow async api middlewares to be executed where required #173
Comments
@VisualBean / @yurvon-screamo is this anything that you recon will be added to core? I have a use case in which I want to have our asyncapi files generated from an AWS Lamda project. The use case of having a way to tie the call to generate the documents with 'UseAsyncApi();' would be a great alternative for me. |
I think it would be a good addition. |
With the current approach of mapping endpoints, we cannot exclude some middlewares (e.g. authoritzation) from execution.
I propose to give full control to the developers (PR coming), similar to what swashbuckle offers.
The text was updated successfully, but these errors were encountered: