Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Async fetch and pagination
See original GitHub issueThere seems to be an issue with AsyncTypeahead and pagination. I’m fetching a list of data from my backend when a user enters in a search query. My backend also paginates the results (as there can potentially be thousands so I’d like to limit the result count). I’d like to be able to pass in a paginate={true} prop whenever there is more data to be fetched from the backend. This doesn’t seem to be working at the moment. From what I gather, the default pagination behavior is to paginate on the options that are already provided which doesn’t allow the options array to grow.
Any thoughts on how to go about this?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
After thinking about it some more, my feeling is that the built-in cache is for basic use cases and pagination falls outside of that. You’d need to make a lot of assumptions about how the pagination works so I think that’s best left to the developer. I added a pagination example as one possible solution, but I imagine there could be lots of variations.
Hey,
useCache={false}fixed the issue and I agree, seems to me like it should work with cached results.