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
Hello,
They could accept this PR (#179), it would be very useful for example to create file managers, not forcing to always have a path from the base path.
In the current situation the url would have to be like this
The implementation in #179 has some performance impact that needs to be considered (extra calls, recursion, etc).
I'll look into ways to reduce it as much as possible...
I'm hesitant to prioritise/consider this due to its limited benefit.
It's possible to register two routes (/file/{path:[A-Za-z0-9\/]+}/{file:[\w,\s-]+\.[A-Za-z]{3,4}} and /file/{file:[\w,\s-]+\.[A-Za-z]{3,4}}) that point to the same handler.
Hello,
They could accept this PR (#179), it would be very useful for example to create file managers, not forcing to always have a path from the base path.
In the current situation the url would have to be like this
/file/{path:[A-Za-z0-9\/]+}/{file:[\w,\s-]+\.[A-Za-z]{3,4}}
with this expression I can make these routes
but i can't do
files/file.jpg
since path is always required.
Thanks for the work.
The text was updated successfully, but these errors were encountered: