I am technical founder of Zato Source and I would like to sponsor the development of a certain feature in chosen, to be used in our open-source product, and I am looking for a JavaScript developer who can do it.
What I would like to see is the ability to type "abc 789" - which means using space-separated keywords - and this would match the latter two options because both of them have "abc" and "789" in their text. That is, the keywords should be and-joined.
Looking at function AbstractChosen.prototype.winnow_results, in chosen 1.8.7, I can see that it builds a regex object that is used for text matching so, tentatively, it seems like there is a need to turn the list of keywords such as "abc 789" into a series of regex objects, and matching each of them, instead of treating input as a single regex pattern.
Note that this is meant to be a mere extension to chosen rather than a replacement of its search capabilities, e.g. it should be still possible to search inside values - this part stays and so do all the other parts of the library.
Feel free to contact me directly if you are interested in this work. My email is dsuch@zato.io.
Hello,
I am technical founder of Zato Source and I would like to sponsor the development of a certain feature in chosen, to be used in our open-source product, and I am looking for a JavaScript developer who can do it.
The feature is multi-keyword search.
Let's say I have these options:
What I would like to see is the ability to type "abc 789" - which means using space-separated keywords - and this would match the latter two options because both of them have "abc" and "789" in their text. That is, the keywords should be and-joined.
Looking at function
AbstractChosen.prototype.winnow_results, in chosen 1.8.7, I can see that it builds a regex object that is used for text matching so, tentatively, it seems like there is a need to turn the list of keywords such as "abc 789" into a series of regex objects, and matching each of them, instead of treating input as a single regex pattern.Note that this is meant to be a mere extension to chosen rather than a replacement of its search capabilities, e.g. it should be still possible to search inside values - this part stays and so do all the other parts of the library.
Feel free to contact me directly if you are interested in this work. My email is dsuch@zato.io.
Regards.