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 have a problem here when moving from version 1.10.0 to 1.11.0 this route is giving a 404 error, this did not happen before in other previous versions.
Whenever I use / before the file name (/api/foo), the error occurs.
I hadn't considered the use-case where a route name looks like a path with a leading /. Is there a reason why you chose this approach?
Route names are intended to be partial module paths (eg. api.foo), since there are many parts of lapis that use the route name to automatically load the corresponding module.
No reason in particular, I just thought the file path would be "views" .. "/api/foo" so I put it with "/" and when updating Lapis it broke some routes on the website, but I already fixed the routes to use without the "/".
Hello @leafo
I have a problem here when moving from version 1.10.0 to 1.11.0 this route is giving a 404 error, this did not happen before in other previous versions.
Whenever I use / before the file name (/api/foo), the error occurs.
Would it be a bug?
The text was updated successfully, but these errors were encountered: