[10.x] Fix for attributes being escaped on Dynamic Blade Components #50471
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.
I understand this is an edge case, but I'm extending the
DynamicComponent
class as I needed some helper methods there:Since v10.48, it fails to pass attributes. This code snippet results in
Argument #1 ($name) must be of type string, null given
:The attributes are filtered out in
attributesToStringWithExistingComponentData()
(see #50403), except for Dynamic Components. However, it only checks for the exact class name, not for subclasses ofDynamicComponent
. This PR fixes that.