You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 2, 2018. It is now read-only.
When server returns empty (zero-length) response and there is no filter specified (filter: false), the autocomplete results are not completely empty length. Instead, the result array is of length one, and its sole element is:
{ data: [], value: "" }
that is, a completely 'empty' item.
I've identified the culprit as the usage of standard JavaScript String.split inside plainTextParser function. For empty strings, splitting with non-empty delimiter produces [""], i.e. an array of one empty string.
I can prepare pull request to fix the issue, but would like to inquire first whether it was an intended behavior or simply a bug.
The text was updated successfully, but these errors were encountered:
When server returns empty (zero-length) response and there is no filter specified (
filter: false
), the autocomplete results are not completely empty length. Instead, the result array is of length one, and its sole element is:that is, a completely 'empty' item.
I've identified the culprit as the usage of standard JavaScript
String.split
insideplainTextParser
function. For empty strings, splitting with non-empty delimiter produces[""]
, i.e. an array of one empty string.I can prepare pull request to fix the issue, but would like to inquire first whether it was an intended behavior or simply a bug.
The text was updated successfully, but these errors were encountered: