AnnotationBuilder::getFormSpecification should accept entity class names #250
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@thestanislav the newly introduced conditional needs a test case |
oprokidnev
pushed a commit
to oprokidnev/DoctrineORMModule
that referenced
this pull request
Apr 19, 2016
Add isser to extract by value
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Doctrine AnnotationBuilder::getFormSpecification should be compatible with Zend AnnotationBuilder::getFormSpecification and should accept Entity class names as parameter.
https://github.com/zendframework/Component_ZendForm/blob/master/Annotation/AnnotationBuilder.php#L178
@param string|object $entity Either an instance or a valid class name for an entity