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
For example, registering a Resource with super('/') and another with super('/test') could result in the former's get (ctx) preventing the latter's getAll (ctx) from functioning.
Requiring Routes and Resources in descending order of number of path components might address this.
The text was updated successfully, but these errors were encountered:
Ghnuberath
changed the title
Do more to check when Resource/Routes paths eat each other
Do more to deal with Resource/Routes paths eating each other
Jun 13, 2018
Courtesy of @ggayowsky, this bug is also related, and a complete pain when two routes match the same request. The current behaviour is that both routes are run, and a 500 is produced due to internal Ravel assumptions that certain middleware (in particuar, Rest.respond only runs once per request).
Unfortunately, there's been no real activity on this issue for a long time, either in koa-router or its official fork @koa/router.
For example, registering a
Resource
withsuper('/')
and another withsuper('/test')
could result in the former'sget (ctx)
preventing the latter'sgetAll (ctx)
from functioning.Requiring
Routes
andResource
s in descending order of number of path components might address this.The text was updated successfully, but these errors were encountered: