James Pudson
60c81e2b69
Update search-query-parser.js
2018-12-23 23:36:03 +08:00
Mathspy
69624744f7
Added offsets and alwaysArray boolean controls
2018-06-10 08:47:52 +02:00
Tristan Jones
d743961ac2
Added support for tokenizing terms, negating terms, and quoted terms
2018-04-04 11:09:38 -07:00
Brad Vogel
d72b16d255
Fix issue where keywords that aren't specified will show up as keywords in the response.
2016-10-28 14:27:07 -07:00
Brad Vogel
23b36fd086
Fix implicit global variable.
2016-10-28 13:11:38 -07:00
Brad Vogel
09a1110f40
Return the character offsets of parsed search parts. The use case is that browser code using the library might want to track the cursor position (eg in an HTML <input> element) to understand which part of the search query the user is editing. It could then show an editor specific to that keyboard, such as a calendar picker, and then splice in the edited value back into the search string.
2016-10-28 12:58:10 -07:00
yangchen
2167fac836
add exclusion syntax
2016-09-27 12:17:11 +08:00
Luiz Freneda
1efb5b1e61
set an empty string when string was not provided
...
preventing TypeError: Cannot read property 'trim' of undefined or TypeError: Cannot read property 'trim' of null
2016-08-31 13:14:28 -03:00
Luiz Freneda
cf8359b8d6
moving ; 😆
2016-08-25 10:32:05 -03:00
Daniel Spofford
5a37692e67
Correctly handle semicolons within search term values
2015-05-04 09:54:17 -05:00
Daniel Spofford
5090897e18
Respect escaped characters while also respecting quoted spaces
2015-05-03 00:11:00 -05:00
Daniel Spofford
a631329ea5
Do not split on spaces inside simple and double quotes
...
Use a regex to identify search terms more reliably than spliting on a space.
Does NOT respect escaping simple or double quotes within a term since JS
does not support look-behinds in regexs.
2015-05-02 21:41:25 -05:00
Julien
fb2a8e2f3b
Add parsing library.
2014-04-07 00:38:47 +08:00
