Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Custom Pull-to-refresh

Open
  • Is something wrong?
#6 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
dart, flutter
Domain
mobile-dev

Research direction

Start by reproducing the provided Column, Expanded, ListView, and footer example, then inspect the current pull-to-refresh integration and the hasScrollBody false path. Done should include a non-throwing layout with pull-to-refresh and a supported way to supply custom pull-to-refresh behavior, including the nested-scroll use case described in the issue.

Written by the indexing model from the issue text.

Description

With your current implementation, it seems that if I have a ListView inside a Column for instance (with a footer), the pull-to-refresh doesn't work.

             Column(
                children: <Widget>[
                  Expanded(
                    child: ListView(
                      children: List.generate(20, (index) => Text('$index')),
                      itemExtent: 100,
                    ),
                  ),
                  Text('Footer'),
                ],
              );

And if I set hasScrollBody: false, it throws.

I guess I would have to use the PullToRefersh directly above the ListView, inside the Expanded.
Maybe the pull-to-refresh should be optionnal or external, so we can use our custom behaviour ?
For instance I could want to implement a custom PullToRefresh component like this.

Thanks.

Dominant language
Dart
Stars
17
Forks
2
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MarcelGarus/flutter_cached

All issues in MarcelGarus/flutter_cached

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.