skip client side input text filtering when request are done serverside #127
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.
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 byprepareUserEnteredText
.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 ifsearchFunction
is defined.If you want, I can make this behavior optional.