Method to clear dataset cache or make it context configurable (page or DOM element)

[jeffmax]

A method for clearing the dataset cache or changing its context from page level to element level would be useful. For larger/long running applications, the page-level cache behavior can be unexpected and undesirable. Providing away to override this, or at least programmatically clear the cache on demand would be helpful. For more justification please see my comment at the bottom of issue #41.

[brianmhunt]

Incidentally, a pull like the one proposed for #95 (pull #220) would permit circumventing the Typeahead.js cache; you could manage your own cache, e.g. with a request management library like amplify.js or model/collection/view manager like Backbone.js.

[andriijas]

I am using mixed sources for my single page app, some backbone collections and some raw prefetch urls. So would still be helpful to notify typehead to clear the cache somehow.

[andriijas]

Please consider this :) Thanks!

[ukilon-okta]

+1 on cache flush.

In a feature I am working on we add resources from the backend, and once resource is added, you can't added again. the way typeahead caches it is impossible to exclude it from the result set.

I ended up cheating and setting a random name + a random string in the URI to work around it, but ideally clearing the cache would be cleaner.

[gesellix]

+1
I would also prefer to programmatically clear the Dataset cache.

+1

[kipwilliams]

+1

[digz6666]

+1

[atronchi]

This should probably be done by default in the destroy method, since if we destroy a typeahead, we generally don't care about the backing store any longer so it shouldn't be kept in memory.

[Crysis21]

+1

[iloveitaly]

👍

[d0nd3r3k]

+1

[richadlr]

+1

[Nelrann]

+1