Merged
Conversation
2 tasks
Member
Author
|
From the PR description
|
emteknetnz
approved these changes
Jul 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes a bad merge-up
I forgot to apply these changes before committing this merge-up.
This PR:
provideSortFieldBecomesIndexes()data provider - it may not actually pass the test, but the format is correct. Fixing the test if it is failing will be a separate follow-up PR. Fixing tests is not part of the merge-up, but updating the style of the provider to match the other scenarios is.array_keyscall to match the other call toDataObjectSchema::deriveIndexFromSort()Issue
default_sortdoesn't take field type into account #11778