ISSUE-153: Solr driven entity autocomplete can not use match operator #154
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
aksm
approved these changes
May 23, 2023
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.
See #153
This removes it and allows the actual field/type of field searched for to deal with "contains". There is no "starts" with in Solr/Lucene but an exact match will happen if the field is a non-full-text string.
Also note for @alliomeria we have been doing this a bit wrong! The actual searched fields are part of the Options on the top, the filter we add is basically "useless". It always uses the configured "fields", the "filters" are used as additional to the the autocomplete match. I hate Drupal sometimes!