Skip to content
This repository was archived by the owner on Sep 23, 2020. It is now read-only.

Analyze the removal of ProxiedApiRouteEndpointLookup in favor of better use of endpoint routing #41

Open
joaofbantunes opened this issue Nov 11, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@joaofbantunes
Copy link
Member

With ASP.NET Core 3.0, there seems to be more focus on endpoint routing (introduced in 2.2).

I haven't really looked at it much, but it might be worth it, to check if we can get rid of the manual routing we're doing with the ProxiedApiRouteEndpointLookup, in favor of using the routing capabilities already present in the framework.

As an example, we can take a look at what MapControllers does, see what we can learn from it.

@joaofbantunes joaofbantunes added the enhancement New feature or request label Nov 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant