[DomCrawler] Fixed a fatal error when setting a value in a malformed field name #8221
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.
Hi,
I found a case where a fatal error happen when trying to set a value in a form field with a malformed name.
In this case,
FormFieldRegistry::getSegments('foo[bar')
method is called and it will returnarray('foo')
only. Therefore the return ofFormFieldRegistry::get('foo[bar')
returns an array instead of aFormField
and so thesetValue()
call happen on the array which leads to the fatal error.I tried to fix that. I don't know if it's the best way to do this so, as always, comments are welcome.