[Pickers][internal] Sort properties #25473
Merged
Conversation
This file contains 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
eps1lon
added
the
component: pickers
eps1lon
force-pushed
the
chore/pickers/sort
branch
from
7c80d59
to
7671b50
Compare
eps1lon
force-pushed
the
chore/pickers/sort
branch
from
7671b50
to
83bc51d
Compare
oliviertassinari
changed the title
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.
Properties are sorted ascending, case insensitive unless they "obviously" belong together. Then we sort them in the order that makes "sense" e.g.
minDate < maxDate(sorting numerically) ordisablePast < disableFuture(sorting temporally).This should help find a specific property in an interface.