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
It would be nice to have the option for a namer for the url as well, and not just one for the upload file structure and download url
Given that we can use a Uri prefix we could use a controller to download the file without necessarily having the url matching the directory structure of the upload because they are 2 different things, the url one would be public facing and the directory namer is internal facing
Right now because of this shortcoming we have to use the same url structure as the file system structure and possibly run more queries than we have to to retrieve the file id from the url
I'm proposing an override option like uri_directory_namer and uri_namer that would be used instead if defined
The text was updated successfully, but these errors were encountered:
I also think this would be a welcomed feature. Until then on way to achieve what you describe is to decorate the used Storage and add custom code for each mapping like so:
Feature Request
Summary
It would be nice to have the option for a namer for the url as well, and not just one for the upload file structure and download url
Given that we can use a Uri prefix we could use a controller to download the file without necessarily having the url matching the directory structure of the upload because they are 2 different things, the url one would be public facing and the directory namer is internal facing
Right now because of this shortcoming we have to use the same url structure as the file system structure and possibly run more queries than we have to to retrieve the file id from the url
I'm proposing an override option like uri_directory_namer and uri_namer that would be used instead if defined
The text was updated successfully, but these errors were encountered: