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
add pagination feature for querys #160
Comments
Once #156 is fully operational it will be possible. We have to document things. My notes for now: Pagination TypesType 1 (I don't know what name to give?)Item form 0 to 9 Type 2 (Infinite Scroll / append)Item form 0 to 9 Pagination Values
|
that's amazing news, very excited! would this also work without manual interaction like clicking a button? e.g. incrementally fetch as much data as there is for a given query and notify me once thats done? |
Once building blocks are in place, I guess that it's not that complicated to do yes 👍 Something like |
that depends on the use case i guess 😄 i want to query the github graphql api for date ranges and then visualize the data. the visualization only makes sense with all the data available. i could of course emualte the behaviour of a user clicking a button until all data has loaded using |
You will definitely not need to create a fake button to click on it 🤣 |
Could you share your operation query? I'm curious! |
haha no, i meant programatically 😄
^ this for example returns the first 100 items for this search, but there are potentially more than 100 items. i want to visualise the entirety of the data, not only the first 100 items. is there an ETA for this feature to arrive? depending on that i would just code the |
You will have a function doing this directly called In your case, you want to "avoid" pagination and get "everything". Fine for 80 items, 102, items, 202 items... |
that's a good point. i was thinking of capping the queries at maybe 1000 elements (would be cool if we could set this cap optionally). if i don't cap it, in my special case the API has a rate limit that will be triggered anyways. |
So you will be able to first: 100 => |
You have it Out-Of-The-Box in Houdini now. |
right now for APIs that need a mandatory
limit
field, there is no easy out of the box way to allow for pagination, filling up the store query by query.the reponse from the query have to be stored outside of the KIT QL store and concatenated with each subsequent queries response.
from a conversation with the author of this library it seems like he is already working on this feature.
The text was updated successfully, but these errors were encountered: