Avoid warning (and dismissal) of objects in input array when using mb_convert_encoding #223
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.
Since commit e5ab4e3, we allow TransactionProcessor::audit $data['diff'] arrays to be handled by mb_convert_encoding (only string was before).
Problem is when an object is inside array (first level or deeper nested), mb_convert_encoding triggers a warning (and object is filtered out of result).
Linked to issue #220