Possible Bug: Call to a member function make() on a non-object

I am writing a package which uses Illuminate\Validation, but when I run phpunit I get the following error message. The package is being used outside of Laravel, but as I understand it Illuminate packages are seperate from Laravel?

PHPUnit 3.7.19 by Sebastian Bergmann.

Configuration read from /vagrant/phpunit.xml

...PHP Fatal error:  Call to a member function make() on a non-object in /vagrant/vendor/illuminate/support/Illuminate/Support/Facades/Facade.php on line 172

I am testing a Validator service in my models directory with the following unit test.

class UserValidator {

    public static function getValidator(User $user)
    {
        $rules = [
            'first_name' => 'required|max:50',
            'last_name'  => 'required|max:50',
            'email' => 'required|email|unique:users,email,' . $user->id
        ];

        $messages = [];

        return Validator::make($user->toArray(), $rules, $messages);
    }
}

    public function testUseServiceValidatorPasses()
    {
        $m = m::mock('Larrytech\Auth\Models\User[toArray]');
        $m->shouldReceive('toArray')->andReturn(['first_name' => 'Joe', 'last_name' => 'Bloggs', 'email' => 'Joe Bloggs']);

        $v = UserValidator::getValidator($m);

        $this->assertTrue($v->passes());
    }

My composer.json has the following dependencies.

    "require": {
        "php": ">=5.4.0",
        "illuminate/support": "4.0.x",
        "illuminate/foundation": "4.0.x",
        "mockery/mockery": "0.7.2"
    },

Many thanks!

[bencorlett]

Validator is a Facade which uses the offsets setup by the IoC in the service providers. It's You'll need to setup your validation environment in a similar sense to how the service provider does.

Once you have your validation environment object setup, you need to call $factory->make(), which is what Validator::make() does in Laravel.

Thanks!

[bencorlett]

You're welcome :)

Sent from my iPhone
Please excuse my brevity

On 08/04/2013, at 8:18 AM, grbsn notifications@github.com wrote:

Thanks!

—
Reply to this email directly or view it on GitHub.

[whatyoubendoing]

Hi there (@grbsn, @bencorlett),

Would either of you be able to let me know how do I go about setting up a Validation environment in a test for testing from a separate bundle?

Thanks
Ben

[ingro]

I've got a similar problem, anyone can provide an example about creating a valid environment? Thanks.

[bencorlett]

Look at how the validation service provider does it. Do EXACTLY that :)

Sent from my iPhone
Please excuse my brevity

On 14/05/2013, at 12:10 AM, ingro notifications@github.com wrote:

I've got a similar problem, anyone can provide an example about creating a valid environment? Thanks.

—
Reply to this email directly or view it on GitHub.

[ingro]

I checked out the validation service provider, anyway in my case it's a bit more complicated cause I'm trying to use it only with the Illuminate/Database package outside a proper Laravel 4 application, so I don't have an $app object to attach the service to.

[bencorlett]

Correct. So you should store the $environment variable somewhere. I do up a little paste for you when I get home.

Sent from my iPhone
Please excuse my brevity

On 14/05/2013, at 5:51 PM, ingro notifications@github.com wrote:

I checked out the validation service provider, anyway in my case it's a bit more complicated cause I'm trying to use it only with the Illuminate/Database package outside a proper Laravel 4 application, so I don't have an $app object to attach the service to.

—
Reply to this email directly or view it on GitHub.

[bencorlett]

Hey mate,

Check out below:

<?php

// Option A:
// Create an instance and use it.

$translator = new Symfony\Component\Translator\Translator('en');
$factory = new Illuminate\Validation\Factory($translator);

$validator = $factory->make($data, $rules);


// Option B:
// Store the factory instance somewhere, Maybe like:

class Validator {

    protected static $factory;

    public static function instance()
    {
        if ( ! static::$factory)
        {
            $translator = new Symfony\Component\Translator\Translator('en');
            static::$factory = new Illuminate\Validation\Factory($translator);
        }

        return static::$factory;
    }

    public static function __callStatic($method, $args)
    {
        $instance = static::instance();

        switch (count($args))
        {
            case 0:
                return $instance->$method();

            case 1:
                return $instance->$method($args[0]);

            case 2:
                return $instance->$method($args[0], $args[1]);

            case 3:
                return $instance->$method($args[0], $args[1], $args[2]);

            case 4:
                return $instance->$method($args[0], $args[1], $args[2], $args[3]);

            default:
                return call_user_func_array(array($instance, $method), $args);
        }
    }
}

$validator = Validator::make($data, $rules);

There are obviously many other ways to achieve what you're after, and you can setup more things with the validator, such as setting the 'presence verifier', for rules such as unique:table,field. Also, just I'm also wire-framing the code above, it's bound to be a bit crappy, but it's a start.

I'd suggest you install illuminate/container though, include all the packages (you'll be using illuminate/database, illuminate/validation and illuminate/translation), create an instance of their service providers by passing in your $container object.

That's a little more complex, but IoC all the things and you'll make yourself smile in the future.

[ingro]

Whoa, thanks a lot for your help! I will try those in the afternoon :)

[ingro]

Your second solution works great, anyway I'm really curious to use IoC to better manage it. I'm sorry to disturb you again, but if I understand well I must use the $container as the App is used on Laravel to attach dependencies on it?