You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the Router.fs has a concept of not_found_handler but RouterEndpoint.fs does not.
Is this by design? What would the alternative be for not_found_handler for endpoint routing?
The text was updated successfully, but these errors were encountered:
Lack of not_found_handler in router and controller - as Endpoint Routing creates global table of routing having scoped not-found handlers is really tricky. Use built-in ways of handle 404 in ASP.NET (such as UseDeveloperExceptionPage)
Hello,
I noticed that the Router.fs has a concept of
not_found_handler
butRouterEndpoint.fs
does not.Is this by design? What would the alternative be for
not_found_handler
for endpoint routing?The text was updated successfully, but these errors were encountered: