Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
$skipflag is now delegated to each filter'sdecodecallback, but none of the built-in filter implementations (json,datetime,point,linestring,polygon,vector,object) accept or inspect this fourth parameter — PHP silently ignores the extra argument. As a result, callingskipFilters(['datetime'])(ordisableFilters()) no longer prevents the decode callback from running; the value is still decoded. The previous code returned early before calling the callback at all when$skipwastrue.External instance filters registered by callers are affected the same way — they receive an undocumented fourth argument they almost certainly don't handle.