-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore File::unique() helper #186
base: develop
Are you sure you want to change the base?
Conversation
@damsfx you also need to add the method signature to the File facade ( |
This pull request will be closed and archived in 3 days, as there has been no activity in the last 60 days. |
* winter.txt, [winter_1.txt, winter_2.txt] -> winter_3.txt | ||
* winter.txt, [winter_1.txt, winter_3.txt] -> winter_4.txt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* winter.txt, [winter_1.txt, winter_2.txt] -> winter_3.txt | |
* winter.txt, [winter_1.txt, winter_3.txt] -> winter_4.txt | |
* winter.txt, [winter.txt] -> winter_1.txt | |
* winter.txt, [winter.txt, winter_1.txt, winter_2.txt] -> winter_3.txt | |
* winter.txt, [winter.txt, winter_1.txt, winter_3.txt] -> winter_4.txt | |
* winter.txt, [winter_1.txt, winter_3.txt] -> winter.txt |
@damsfx it should probably allow the input to be returned unmodified if it doesn't exist within the array.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@LukeTowers If the entry doesn't exist in the array, it must be returned with another index anyway, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@damsfx I'm making the suggestion that if it doesn't exist in the array it should be returned unmodified. The method is intended to give you a unique filename provided the input of a desired filename and a list of already existing options. If the filename provided is already unique, then there's no need to modify it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@LukeTowers So in a such case, the same filename is needed in the array of references to get the next incremented name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The suggested change above should list all the cases that I think the method should need to handle, I've already updated the tests so it should just require a minor change in the method itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@LukeTowers Your modifications in tests goes to a failure for me.
// File already unique, return original
'winter.cms' => ['winter.cms', ['winter_1.cms']],
FAILED !
The function return wintert_2.cms
in that case.
What I don't understand is why you want to return the unmodified value if it's unique.
In any case, we should return the incremented value! 🤯
(new Filesystem())->unique('winter.cms', ['test.cms']); // winter_1.cms
(new Filesystem())->unique('winter.cms', []); // winter_1.cms
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@damsfx The tests are failing because the method doesn't currently have the logic to allow the name to be returned unmodified. The method claims to return a unique filename given the input of a desired filename and a list of existing filenames; why does it have to always return an incremented value if the desired filename isn't present?
Restore :