[8.x] Arrayable/collection support for Collection::splice() replacement param #39592
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 there,
Behavior
The
Collection::splice()
's$replacement
parameter has different behavior depending on whether a collection or array is passed in. I expected this to be the same. Example:This is due to the way PHP's native
array_splice
method handles objects. Although, I think this is unexpected for the user.Backwards compatibility
Backwards compatibility is broken for all objects which implements
Enumerable
,Arrayable
,Jsonable
,JsonSerializable
orTraversable
. Other types are cast to anarray
by thegetArrayableItems()
method, which is similar to whatarray_splice
does. The latter does not break backward compatibility.