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
'source' for Dataset #206
Comments
You can do some advanced configuration that will allow you to do things like preprocess the URL to send to, or post-process data, etc.—the docs for that are here: https://github.com/twitter/typeahead.js#remote |
@gemshare-jonathan - would this issue be resolved with pull request #220 (or some equivalent?) |
@brianmhunt thanks - #220 looks like what we need. I read your comments and I am not sure when/why we need both computed and remote on the same dataset. It seems computed should be a variant of remote. things like rate limiting is still useful for computed. any luck on getting #220 reviewed and merged? |
Thanks for the comments. Under issue #95 there is some discussion of the rationale for adding Since One can always do rate limiting oneself with |
I've had a lack of free time over the past month and I haven't been able to deal with typeahead.js issues as thoroughly as I'd like. Things should start to settle down for me within the next week or two and that's when I'll be able to take a look at issues/PRs in a bit more detail. |
You can now define a custom source for your data in v0.10, so I'm going to go ahead and close this issue. |
From discussion on #95
The use case is to get data from a function, which wraps calls to 3rd party APIs that do not expose an URL, such as Google Places.
The text was updated successfully, but these errors were encountered: