bug: Fix ObjectPropertyRipper
to handle stdClass
objects
#65
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.
Currently, attempting to rip from a
stdClass
will fail with an error that it is not possible to bind a closure to the scope of an internal object.It should not normally be necessary to call any of the
rip
methods for astdClass
, because by definition all props are public so the result will be the same as$vars = (array) $object
.However, it can cause a problem if e.g. calling the ObjectPropertyRipper recursively to dump an entire object graph where the tree may include some stdClass instances. Our methods are typed to accept any kind of object, so should work with
stdClass
rather than requiring the caller to check this externally.