Yes.

Why string attributes returns empty when is not empty on Laravel Form Request Object?

When you do $request->image you are calling the __get method from Request and getting the returned value. The empty function only works with variables (php.net/empty).

Hey @beeblebrox3 thx for reply, btw testing this again, work like expected with pure php (5.6):

    public function test()
    {
        return 'b';
    }
    var_dump(empty($this->test())); #bool(false) 

Yeah, sorry about that.

Look this gist: https://gist.github.com/beeblebrox3/0b5c2efd176ce3c4370e
When I do empty($obj->a) the __get method is not called.

Technically, $obj->a doesnt exists, so empty will return true

@GrahamCampbell Look, it's really a Laravel bug. When you do empty($instance->property) it will check first for __isset() method on $instance and after for __get() method.

In this case, nether FormRequest or Request or ArrayAccess defines the __isset() method. And it is needly to it works. And considering that you are working with a FormRequest, you should be capable to do it.

Currently you should "hack" to make it works property, by two ways (but not that it's a workaround):

• Copying attribute to variable: $value = $instance->value; then empty($value)
• Force casting to jump over __isset(): empty( (string) $instance->value )

It' isn't laravel bug (yea, it's laravel bug): https://gist.github.com/kneipp/aee5802d08505d605676

[Gist updated]

Yes, it's. Note that empty() fail on line 16 because you not have defined the method __isset(). And empty() will first try call __isset() and, only if it returns true, __get() will be called.

Try to define this method and you will see that __get() will be called as should be expected.

Yea, we're right it's a laravel bug.