MNT Conflict with silverstripe/framework 5.1.0 #5
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.
That version will require a new minor release of this module, which there's already a PR for, due to conflicts in the method signature of the new ArrayList::excludeAny() method and that method in the searchfilterable arraylist.
This is really just to make CI happy - in a real project the conflict won't be necessary since composer will just grab the most recent version anyway.