-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Expose ApiDescriptionProvider types and methods (so other projects can use it) #39459
Comments
Thanks for contacting us. We're moving this issue to the |
Similar issue: #33644 |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
Any updates on this for 2024 NET9 release? cc @captainsafia , thanks for tracking this |
@jkone27 Hey -- sorry I hadn't seen this issue before. 😅 With regard to solving the issues that you referenced in the original bug report, does the guidance that I recommended in giraffe-fsharp/Giraffe#488 (comment)? If so, it would be good to get a sense of what specific APIs need to be consumed. How is making |
I see in Oxpecker and Falco the maintainers managed to implement something for openapi descriptors, they are both F# FP wrappers on top of AspNet core, some discussions there I can link them here if u are interested, sorry for the late reply |
Endpoint Metadata Parsing methods are not accessible
Many third parties might be interested in retrieving metadata from endpoints for e.g. openapi spec generation
https://github.dev/dotnet/aspnetcore/blob/94ffe0356177368d73f98021da53456fc658fcd4/src/Mvc/Mvc.ApiExplorer/src/EndpointMetadataApiDescriptionProvider.cs#L28
Describe the solution you'd like
It would be appreciated if metadata from endpoint could be easilly navigated and extracted (e.g. Expression of invoked lambda/delegate, main properties of lambda/delegate, return type, parameters type, HTTP method name, etc....)
that way endpoints could be inspected at runtime just checking
but right now it's hard and very tough to do especially for NON MVC projects (even requires quite elaborated reflection to access endpoint info...)
Additional context
pimbrouwers/Falco#49
giraffe-fsharp/Giraffe#488 (comment)
giraffe-fsharp/Giraffe#428
giraffe-fsharp/Giraffe#488
SaturnFramework/Saturn#30
The text was updated successfully, but these errors were encountered: