You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lfarrel6 opened this issue
Aug 29, 2022
· 4 comments
Assignees
Labels
A-outputOutput displayedE-featureFeature requestI-apiInternal API changeO-dynamicDynamic outputX-api-addAddition to the external api; No risk of downstream breakage
I'd like to use minus to display paginated data that is pulled from an API. Ideally, the data would be paginated as the user scrolls through the logs, in a similar manner to an infinite scroll component.
Proposed Solution
An additional config on the PagerState, similar to the exit callback vectors. The callback should be fired when the user reaches the end of the currently available data.
Alternative
There's no clear alternative — while minus supports streaming data in, there's no obvious way to fetch more data at the rate that the user is consuming.
I am happy to contribute the changes to include this in the library.
The text was updated successfully, but these errors were encountered:
Currently I am busy incorporating a native user input declaration system inside ninus so it might take a while for me to work on this. If you want to help, you're are very welcome to file a PR.
For any help, join our Matrix or Discord rooms. Thanks again.
Hey I just wanted to ping you whether you are ready with your PR for this issue. I am planning for a small release so if your PR is ready I will include it in the the release.
A-outputOutput displayedE-featureFeature requestI-apiInternal API changeO-dynamicDynamic outputX-api-addAddition to the external api; No risk of downstream breakage
Feature description
I'd like to use minus to display paginated data that is pulled from an API. Ideally, the data would be paginated as the user scrolls through the logs, in a similar manner to an infinite scroll component.
Proposed Solution
An additional config on the PagerState, similar to the exit callback vectors. The callback should be fired when the user reaches the end of the currently available data.
Alternative
There's no clear alternative — while minus supports streaming data in, there's no obvious way to fetch more data at the rate that the user is consuming.
I am happy to contribute the changes to include this in the library.
The text was updated successfully, but these errors were encountered: