-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reinitialize Typeahead with new source #27
Comments
Sorry, I'm struggling to understand your use-case in this scenario. You can attach more than one Bloodhound object to a single typeahead control on initialisation. However, you are saying that you wish to switch suggestion engines half-way through the typeahead receiving input? Can you provide an example of why you'd need this functionality, over say, two separate typeahead controls, or a single bloodhound object with all combinations of both numbers and letters, or a simple text input with a Regex validation? |
I have two bloodhound objects... And yes.. I wish to switch objects half I hope you understand my case.
|
I'm afraid that this isn't a use-case that I can easily support, as Twitter Typeahead simply isn't designed to be used in this way. |
Firstly, many thanks for this angular method of using typeahead!
My use case has brought me to a grinding halt. Ill try to describe it as best i can..
Essentially, I have two 'sources' from which I want typeahead to suggest from. I am using the bloodhound engine. So, I have initialized two Bloodhound objects - one, numbers.initialize() and two, letters.initialize(). Problem is, when I intiialized typeahead at fist using source:numbers.ttAdapter() it obviously works as expected.. But, on selection of an item from typeahead, I want to change the source to source:letter.ttAdapter(), since according to my use case, I want another source to be used for suggestion. What could be the best way to do that? Any way to reinitialize typeahead programatically with a new source?
The text was updated successfully, but these errors were encountered: