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

skip client side input text filtering when request are done serverside #127

Closed
wants to merge 1 commit into from

Conversation

azmeuk
Copy link
Collaborator

@azmeuk azmeuk commented Jan 19, 2022

I encountered a usecase where filtering was done serverside, and a user input contained a dot ., but the server response seemed incoherent. I saw that the dot was deleted by prepareUserEnteredText.

If filtering is done serverside (i.e. there is a searchFunction) then the input cleaning (i.e. prepareUserEnteredText) should also be done serverside.

With this patch, prepareUserEnteredText is not called if searchFunction is defined.

If you want, I can make this behavior optional.

@pstanoev
Copy link
Owner

Added new option:
cleanUserText=false which expicity controlls if prepareUserEnteredText is called.

Available in the new version 2.3.0.

@pstanoev pstanoev closed this Feb 24, 2022
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.

None yet

2 participants