Support instanciation of object with named constructor #303
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently having a private constructor will force instanciation using reflection (using instanciator
ReflectionWithoutConstructor
).Current implementation only allows to use factory method when the class constructor is public.
This is not working when using the Named constructors (http://verraes.net/2014/06/named-constructors-in-php/)
This PR intends to provide the use case describing this scenario and open discussion about the best way to handle it.
So far, I've tried to manipulate the
ReflectionWithConstructor
andReflectionWithoutConstructor
canInstantiate
method, but I can't make the whole test suite pass.