Case insensitive custom field params#15404
Merged
brandonkelly merged 2 commits into5.3from Jul 24, 2024
Merged
Conversation
|
@brandonkelly The addition of caseInsensitive is great for querying, but is there a solution for ordering? I have a use case where I need to sort by Company Name and there are some companies names which are correctly stored as lowercase but I'd like them sorted case insensitively, is this possible? |
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
2 participants
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.
Description
Color, Country, Email, Icon, Link, Plain Text, and Table fields’ element query params now support passing in an array with
valueandcaseInsensitivekeys.{% set entries = craft.entries() .section('locations') .email({ value: emailValue, caseInsensitive: true, }) .all() %}Related issues