Skip to content
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

Open
ch-ti8m-michalpenka opened this issue Aug 23, 2023 · 2 comments
Open

Comments

@ch-ti8m-michalpenka
Copy link

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.

@yvanruth
Copy link

yvanruth commented May 2, 2024

@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.

@VisualBean
Copy link
Collaborator

@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.
However can you elaborate on your usecase? Just so we keep it in mind?

smoerijf pushed a commit to smoerijf/saunter that referenced this issue Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants