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
Endpoints Explorer Support #539
Comments
i couldn't find any info/docs about how VS actually discovers the endpoints. most definitely not by looking at the endpoint data sources in memory, otherwise it would have shown up. most likely by static analysis looking for .Map*() methods in the source code like how their new request delegate generator discovers endpoints. rider on the otherhand picks up endpoints when i give it the location of the swagger.json file. maybe there's a way to get VS to do the same via swagger.json? will do more digging around but since VS is closed source, doubt we'd have much luck. |
If nothing else it should pick up requests from .http files but it doesn't do that, either. You can apparently create .http files from Endpoints Explorer but not the other way around. So far (because I always use endpoints) I haven't found Endpoints Explorer to be at all useful... |
yeah even in rider I don't find myself using the endpoint explorer ever. just like to work with .http files or swagger ui for quick testing of endpoints. postman doesnt even get much action from me anymore 😋 anyway let's keep this issue open and implement it as a "nice to have" feature if we can figure something out without having to invest too much energy in to it. |
Right. I'm hoping we can get the Visual Studio team to figure out how to detect our endpoints. |
yeah that would be great... |
There are already some open VS feature requests linked from this similar issue: Specifically: Feel free to upvote them, everyone! |
everyone who's interested in seeing FE endpoints in VS endpoints explorer, please go vote/comment on this issue. |
Not sure if it's related, but Rider also cannot detect any Fast Endpoints endpoints |
@frasermclean rider does pick up |
By default Fast Endpoints endpoints don't appear to be automatically discovered by VS 2022's Endpoints Explorer. I'm not sure if there's anything we can do or if we need to relay on Visual Studio to address this but we should track it.
The text was updated successfully, but these errors were encountered: