-
Notifications
You must be signed in to change notification settings - Fork 201
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
Missing the ability to insert Sliver children #122
Comments
Hi @creativecreatorormaybenot , |
@EdsonBueno Why do you think that this is not possible? The way you do it is by placing the sticky headers as slivers into the The reason this is not possible with |
By doing this, we would loose the ability to build children on demand, since |
@EdsonBueno You can implement the same logic using a That is also what I am saying btw - this is possible without pagination / a builder, but with the pagination package it is not possible at the moment. It would of course need to be implemented. |
We need this feature. For now, we can use this plugin to use sticky headers inside listview https://pub.dev/packages/sticky_headers |
Adding some more example to this request. I stumbled upon exactly this same problem recently. My use case is as follows:
I stumbled upon this example for sticky header which uses sliver_tools for sticky header. They use simple trick of returning a The way |
Feature request
This request is similar to #48, however, the use case is actually not yet covered by the package (not that I know). Namely, we need section headers, which requires to have slivers as children of the paged list.
Current support
What you can do currently is implement a sticky header:
However, you cannot have section headers, i.e.:
Proposal
It would be nice to have a version of the
PagedSliverList
that allows to have aPagedSliverBuilderDelegate
that allows you to returnSliver
s instead of regular widgets (render box contract).@EdsonBueno if you have another idea how to solve this, let me know.
The text was updated successfully, but these errors were encountered: