Conversation
Miles-Alford
approved these changes
Jul 5, 2024
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.
Link to JIRA ticket
https://hackney.atlassian.net/browse/TS-1466?atlOrigin=eyJpIjoiNTk1MDEwMDJlMjg4NGI4ZjhlZDMzMjJkNjg4MmU5NjMiLCJwIjoiaiJ9
Describe this PR
What is the problem we're trying to solve
I want to be able to make a query that can test a split wildcard property (i.e. 123 & example) is both true on a field.
What changes have we introduced
Adds a method that allows for individual boolean wildcard queries on an elastic search.
Checklist
Follow up actions after merging PR
Will be implemented in the search-api as LBHackney-IT/housing-search-api#230