I ran into the issue where I was searching/filtering the mentions data via remote http calls, and then updating state with the newly filtered data. However, the library then also filters the data using some string matching. The issue is that we allow searching by more than just the display value, and so results coming from our remote search wouldn't show up in the list because the library filtered them out.
This adds a 'disableLocalSearch' option that skips the local searching/filtering if it is true. It defaults to false for backwards compatibility.
I ran into the issue where I was searching/filtering the mentions data via remote http calls, and then updating state with the newly filtered data. However, the library then also filters the data using some string matching. The issue is that we allow searching by more than just the display value, and so results coming from our remote search wouldn't show up in the list because the library filtered them out.
This adds a 'disableLocalSearch' option that skips the local searching/filtering if it is true. It defaults to false for backwards compatibility.