Add a ReflectionPropertyAccessor

[ogizanagi]

I use this accessor mainly for hydratation because my domain objects do not have proper setters for every properties, or in order to set predictable values for those computed directly in the constructor.
However, I wonder if it should be wired by default or not.

[theofidry]

I'm ok to add this accessor as it can be useful, I however wouldn't wire it by default. I actually removed that behaviour in 3.x (setting properties by accessing them directly) because it was causing too many issues

It would also be nice to add a doc entry for it as well :)

[theofidry]

you should add a test with a private static property

[ogizanagi]

You mean to ensure the accessor never consider static properties? Done (and accessor updated).

[theofidry]

(CS)

$getPropertyClosure = \Closure::bind(
    function ($object) use ($propertyPath) {
        return $object->{$propertyPath};
    },
    $objectOrArray,
    $objectOrArray
);

[theofidry]

return (new \ReflectionClass($class))->hasProperty($propertyPath);

(I would keep the $class though)

[theofidry]

hm, the order doesn't seem right, I really need to add a StyleCI...

[ogizanagi]

Changes made. :)

Where would the documentation fit the best in the current documentation? (mention the decoration of the loader property accessor + symfony configuration sample)

[theofidry]

I would say here and maybe mentioning it there as well:

You can reference properties reachable through a getter (i.e : @name->property will call $name->getProperty() if property is not public)

[theofidry]

Shouldn't it be able to read it?

[ogizanagi]

I don't think we should support it (use cases look a bit edgy to me), but you set the rules. 😄

Actually, I'm not even sure the property access component is meant to be used to access any static property.

[ogizanagi]

Documentation added.