• Removes call to non-existent method ‘checkBit’
• Uses $recursive option passed as 2nd argument to determine if recursion should occur
• Removes unused argument from DirectoryHandle::buildNodesRecursive

Is it possible to use this as file system for JSON-RPC where client is command line app in a browser? Or this FS vanish when the script end. Is it possilbe to save reference to VFS in a $_SESSION?

Trying basic code from example, but is_readable() returns false, while file_get_contents() returns contents without problems. I assume this is because it's stream and looks like is_readable() returns false for streams.

Any idea/workaround for this?

Seems like is_dir() does not work with a virtual directory. My guess is something is not completely correct with the value of $directory->getMode(), but I'm not sure.

Test case to reproduce the issue

<?php

namespace Vfs;

use Vfs\Node\Directory;
use Vfs\Node\File;

class PHPFileFunctionsTest extends \PHPUnit_Framework_TestCase
{
    const SCHEME = 'foobar://';

    /**
     * @var FileSystem
     */
    private $fs;

    public function setUp()
    {
        $fs = FileSystem::factory( self::SCHEME );

        $someDir = new Directory( array( 'file' => new File( 'foobar' ) ) );

        $fs->get( '/' )->add( 'some_dir', $someDir );

        $this->fs = $fs;
    }

    public function tearDown()
    {
        $this->fs->unmount();

        unset( $this->fs );
    }

    public function testFileGetContentsWorks()
    {
        $path = self::SCHEME . 'some_dir/file';

        $this->assertEquals( 'foobar', file_get_contents( $path ) );
    }

    public function testIsDirWorks()
    {
        $path = self::SCHEME . 'some_dir';

        $this->assertTrue( is_dir( $path ) );
    }
}

Output from running PHPUnit:

There was 1 failure:

1) Vfs\PHPFileFunctionsTest::testIsDirWorks
Failed asserting that false is true.

/home/vagrant/src/github/vfs.php/test/unit/PHPFileFunctionsTest.php:46

FAILURES!
Tests: 163, Assertions: 379, Failures: 1.

While symlink() isn't supported by PHP Stream Wrappers to create symlinks, you can still interact with symlinks that already exist.

<?php
use Vfs\FileSystemBuilder;
use Vfs\Node\FileLink;

$fs = (new FileSystemBuilder())->setTree(['foo' => ['bar' => 'baz']])->build();
$fs->get('/')->add(new FileLink('my_symlink', $fs->get('/foo/bar')));

is_link('vfs://my_symlink'); // => true

They're actually implemented as hard links rather than symbolic links, meaning that if the target file is moved or renamed the link still works. It was easier to implement this way.

adlawson/vfs.php now has a Chat Room on Gitter

@adlawson has just created a chat room. You can visit it here: https://gitter.im/adlawson/vfs.php.

This pull-request adds this badge to your README.md:


Happy chatting.

PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

This triggers the symfony debug class loader with the following:

  1x: The "Vfs\Stream\AbstractHandle::rename()" method will require a new "string $origin" argument in the next major version of its interface "Vfs\Stream\HandleInterface", not defining it is deprecated.

The mismatch triggers symfonys debug class loader with:

  1x: The "Vfs\Node\Factory\NodeFactory::buildFileLink()" method will require a new "FileInterface $file" argument in the next major version of its interface "Vfs\Node\Factory\NodeFactoryInterface", not defining it is deprecated.

Changes at this stage are sometimes quite large. Good thing is that not many people use this library so I can get away with it for now but I should really add a useful changelog.

Some of the time, especially when opening a file/directory handle, the open mode is taken into account (w vs w+ vs xt etc). The mode and modifier both need to be taken into account when reading/writing/deleting handles.