fix: Anonymous class support for ReflectionHelper

[neznaika0]

Description
I'm doing another PR and in the tests I found that anonymous classes cannot access parent properties. I hope this fixes it.

I want to note that there will be problems when both classes have the same properties - the reflection of the helper changes only the child. Any suggestions?

Example:

// Foo class
$obj->private = 'root';

// anon class with Foo
$child->private = 'child';
// helper will only change the child, the parent will contain the old value 
// for example, call from the root method
$child->getPrivate() // root

The guide, as always, corrects the translation.

Checklist:

• Securely signed commits
• Component(s) with PHPDoc blocks, only if necessary or adds value (without duplication)
• Unit testing, with >80% coverage
• User guide updated
• Conforms to style guide

[neznaika0]

If you know how duplicate properties should work correctly, you can fix it here. When properties exist in both classes

[michalsn]

I don't think this is a good idea.

Reflection exposes class semantics as they are. Private properties belong strictly to the declaring class. Automatically scanning parent private properties would make private appear inherited, which it is not. The helper would introduce a misleading abstraction, so the current behavior should remain unchanged.

[neznaika0]

@michalsn In my opinion, if we need access to private properties, are we allowed to change the parent values?
Is that the idea of an helper, not?

[michalsn]

A helper should make common tasks easier, not redefine visibility rules. Parent private properties are not part of the child's API, and Reflection does not change that.

[neznaika0]

Sadly. Overdoing it again. Let's wait @paulbalandan @samsonasik

Do you think it's okay to duplicate private properties in an anonymous class? The parent will not change, only the child.

[paulbalandan]

In this example:

// Foo class
$obj->private = 'root';

// anon class with Foo
$child->private = 'child';
// helper will only change the child, the parent will contain the old value 
// for example, call from the root method
$child->getPrivate() // root

in my opinion, $child->getPrivate() should return the private property of the child class as it has no knowledge of the parent's private properties. The same should go with reflection.

[neznaika0]

Good. This is still a problem if you really need to get a private value. Can we move it to new methods and specify it as 'feat'?

[michalsn]

Good. This is still a problem if you really need to get a private value. Can we move it to new methods and specify it as 'feat'?

I'm against this. Mocking private parent state couples tests to implementation details rather than behavior, which is generally a design smell and not something helpers should normalize.

[neznaika0]

We won't keep PR for long. Maybe someday it will be useful for a personal project.
Thanks for your opinion.