Issue #186 : allows "array" db type to be used with a collection form type #284
Conversation
This file contains hidden or 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
|
Thanks @pierrerolland Could you please duplicate for Propel guesser? |
|
You're welcome, @sescandell :) Hasn't it been corrected for Propel guesser by this commit ? 0d6c9a8 |
|
You're right! Thanks again |
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.
Collection types currently have to have a Doctrine mapping association. That makes simple array type unable to be used as a collection type.
In this "fix", we check, when there is a collection type, if the column has a mapping association before getting it, to avoid the "No mapping found" error reported here : #186