-
Notifications
You must be signed in to change notification settings - Fork 35
Zend\Filter\File\RenameUpload behaves differently when folder exists and not #4
Comments
@svycka I've checked it and I believe it is desired behaviour. As target we can provide the directory or the file name and in script we can't recognise what you have on mind. So:
|
@webimpress I do not agree with you
sounds ok.
this is not documented so I am not sure how you decided this is the desired behavior. Don't understand how having two hidden behaviors from one option is good. maybe new |
@svycka Ok, reopening. Feel free to submit PR - either: documentation update of propose a fix. |
fixing would mean BC break? if this is the desired behavior |
@svycka If you propose fix which will be BC Break we will plan it for v3. I've described what is the current behaviour, and, yes, I can see it can be a bit tricky, but I think it is logical. There is not anything like 'file prefix' right now, the provided target is either directory "where file should be moved" or the new file name. As you are using |
This repository has been closed and moved to laminas/laminas-filter; a new issue has been opened at laminas/laminas-filter#13. |
code example:
when
logo
folder exists returned value would be:when
logo
folder doesn't exists returned value would be:I can't beleave this is desired behavior because this can lead to bugs.
Guess I used this incorrectly because I wanted logo prefix this worked for me until someone created logo folder then everything gone bad :(
The text was updated successfully, but these errors were encountered: