Accent insensitive search feature #177
Open
Conversation
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
1 participant
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.
This PR , proposes a solution to handle accent insensitive searches , just like case sensitiveness .
The default value is
accent insensitive search.And the query
Divisionmatches both forDivisionandDivisón.Now
:accentSensitiveTags={Boolean value}can be used in <tags_input> to alter the functionality.BEFORE :
AFTER :
The only thing not working for me is on the clicking on the checkbox , the value of accentSensitiveTags doesn't change , in the dev env.
Can someone help with that ?
Apart from this , setting the value to both true and false manually , has gotten me the desired results.
Thanks.
Issue #174