This repository has been archived by the owner on Jan 8, 2020. It is now read-only.
Fix for #6263 (replaces PR #6518) #6880
Closed
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
This was referenced Nov 15, 2014
|
IMO Collection shouldn't accept ElementInterface at all...restricting Collections to containing only FieldsetInterface simplifies the populate and extract logic. But that's a discussion for ZF3. |
|
@adamlundrigan manually merged: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Issue summary
Elements of type
Zend\Form\ElementInterfacecannot be added directly to a Collection object due to the latter's setting of an object prototype on the supplied element, which is only defined onZend\Form\FieldsetInterface.Fix
Handle
Zend\Form\ElementInterfaceinstances separately; callsetValueinstead ofsetObject.Ack
Fix and reproducing code snippet contributed by @SteveTalbot