-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Filter listview by terms #2092
Comments
I think we can also close this because we landed a solution. |
There has been no solution found for this, and has nothing to do with my other pull request directly. I believe this is a much more basic issue that still needs to be addressed. It's not about search cases or regex or any of that, but rather simply the fact that if you have the string "lastname, firstname" in a listview the user can't filter down to this by typing "firstname, lastname" |
Re-opening this our hook doesn't really cover this. |
I just tagged as a feature request...can you add this to the feature request wiki, link to this issue, then close it? We'll re-open when we tackle this. |
ok here is the pull request that I had submitted for this before (which you also closed at the same time): I had also added it as a feature request before. Check out: I think there has been some kind of confusion as I was trying to get the two things settled concurrently... We currently have it hacked into our code which is about to be a live release, as no one dealing with UX (or myself) could imagine a filter function being limited to an exact match these days, considering the expectations based on what other mobile sites and native applications are delivering. I'm guessing this will mean maintaining our own listview filter project, or moving to another framework in the next iterations - at least for a while. |
The listview filter is a match on entire string rather than terms.
rather than filtering once on a single string per
<li>
there should be an option to filter based on terms within the string (eliminating the need for full matches or exact order). This is easy enough to accomplish, but it might be best as an optional functionality due to increased overhead.I am mostly creating this to have a ticket number for reference as I already have a solution that is enabled with data-filter-terms="true". In this case I actually ended up repeating the filtering process with each term entered rather than splitting all li's into possible terms over and over again. I am debating whether or not my feeling that this way incurs less overhead is correct, but at least it would be taking advantage of the existing methods.
The text was updated successfully, but these errors were encountered: