Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: prevent filtering out synonyms #38

Closed
wants to merge 1 commit into from
Closed

fix: prevent filtering out synonyms #38

wants to merge 1 commit into from

Conversation

willopez
Copy link

Synonyms are incorrectly filtered out.

Related issue: #29

A corresponding PR in reactivesearch will be necessary to call getSuggestions without currentValue

@janus-reith
Copy link

Will this be merged soon?

@siddharthlatest
Copy link
Member

currentValue is a good default in most scenarios (when data isn't unique), so I don't feel great about removing it altogether.

I am closing this PR as the intent behind it should already be addressed by using the unparsed suggestions https://opensource.appbase.io/reactive-manual/advanced/customsuggestions.html. If there is a bug with that behavior, we should address it in ReactiveSearch rather than here. I did check the current codebase, and it should work as intended from what I can tell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants