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
When I am using Finder correct, it destroys file names containing whitespaces when using built-in sorting features (for instance Finder::sortByType()). Sorting with Closures works as expected.
1) Test::testWithBuiltInSorting with data set #0 ('/tmp/finder-test/2012-10-28T15:27:41+01:00', '/tmp/finder-test/2012-10-28T15:27:41+01:00/HELLO WHITESPACE!')
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'/tmp/finder-test/2012-10-28T15:27:41+01:00/HELLO WHITESPACE!'
+'/tmp/finder-test/2012-10-28T15:27:41+01:00/HELLO'
The text was updated successfully, but these errors were encountered:
This PR was merged into the master branch.
Commits
-------
2817a47 [Finder] Fixed filename containing space bug in gnu adapter.
9bf7cb0 [Finder] Added filename containing space to tests.
Discussion
----------
[Finder] Fixed filename containing space bug in gnu find adapter.
Bug fix: yes
Feature addition: no
Backwards compatibility break: no
Symfony2 tests pass: yes
Fixes: #5851
`GNU find` adapter now uses `cut` instead of `awk`.
When I am using Finder correct, it destroys file names containing whitespaces when using built-in sorting features (for instance
Finder::sortByType()
). Sorting with Closures works as expected.Example:
/a/b c
will be cut to/a/b
.OS: ArchLinux, Linux 3.5.4-1-ARCH
FS: EXT4
PHP: 5.4.7 (cli)
Finder: 2.2-dev
Test: https://gist.github.com/ec2bb92a2c65133187c8
The text was updated successfully, but these errors were encountered: