Flutter_cached_network_image: Is this still supported?

Created on 29 Aug 2018  路  6Comments  路  Source: Baseflow/flutter_cached_network_image

Cached Images is such a crucial feature for flutter, but from the issues and PRs comments it seems this is not supported anymore?

Is there an alternative or somebody who would be willing to take this over?

Every time I upgrade my flutter dev channel this breaks and I have to use somebody's fork to keep on going. That is not really acceptable for something so integral and important to flutter as Cached Images should be and makes flutter look unprofessional.

Cached Images should be actually part of the core flutter libraries.

Most helpful comment

It looks like the maintainer is not really doing anything anymore.

It seems like @Cretezy is actually working on this and has many fixed things in his fork. I would vote for @Cretezy to take over this project (and as well flutter_cache_manager) or at least be a maintainer of it. (See: https://github.com/Cretezy/flutter_cache_manager and https://github.com/Cretezy/flutter_cached_network_image)

@renefloor can you give @Cretezy full access to this repo (and as well flutter_cache_manager) so he can push, merge, ...? As well please allow @Cretezy to push to the dart hub.

How to do it:

  1. Add @Cretezy as collaborator here: https://github.com/renefloor/flutter_cached_network_image/settings/collaboration
  1. Add @Cretezy as upload on dart pub:
    pub uploader add [email protected] (guessing the e-mail is right)

  2. (optional, or can be done by @Cretezy) Add @Cretezy as author to pubspec.yaml:

# Add this below instead of: author: Rene Floor <[email protected]>
authors:
- Rene Floor <[email protected]>
- Charles Crete <[email protected]>
  1. Do the same for https://github.com/renefloor/flutter_cache_manager as well (as well here @Cretezy fixed several things already)

All 6 comments

It looks like the maintainer is not really doing anything anymore.

It seems like @Cretezy is actually working on this and has many fixed things in his fork. I would vote for @Cretezy to take over this project (and as well flutter_cache_manager) or at least be a maintainer of it. (See: https://github.com/Cretezy/flutter_cache_manager and https://github.com/Cretezy/flutter_cached_network_image)

@renefloor can you give @Cretezy full access to this repo (and as well flutter_cache_manager) so he can push, merge, ...? As well please allow @Cretezy to push to the dart hub.

How to do it:

  1. Add @Cretezy as collaborator here: https://github.com/renefloor/flutter_cached_network_image/settings/collaboration
  1. Add @Cretezy as upload on dart pub:
    pub uploader add [email protected] (guessing the e-mail is right)

  2. (optional, or can be done by @Cretezy) Add @Cretezy as author to pubspec.yaml:

# Add this below instead of: author: Rene Floor <[email protected]>
authors:
- Rene Floor <[email protected]>
- Charles Crete <[email protected]>
  1. Do the same for https://github.com/renefloor/flutter_cache_manager as well (as well here @Cretezy fixed several things already)

It's definitely not a good look for Flutter. I'm updating a few projects I've made to Flutter v0.6.0 and Dart 2.0.0 and having libraries stop working and no longer being maintained is VERY troubling. These are projects that were working a month ago!

Yeah, I definitely plan on maintaining the packages when my time allows it. I use these plugins myself, so maintenance will happen and my fork will still be alive, although new features from myself will be rare (accepting PRs though!)

@renefloor I'd be happy to maintain these for you. Shoot me an email at [email protected] (might not be my Pub email if you plan on adding me as an uploader)

Sorry guys, I have had a very busy and heavy time last half year so I had to ignore this project. That is all done now so I will maintain this project again from now on. This week I will update all used packages so everything is compatible again. I am also planning to rewrite large parts, for example to use sql to store the cache data. I will carefully look at all pull requests which makes sense to incorporate and which don't. (Also with the rewrite in mind.)

@Cretezy thanks for the offer. It is a good idea to have a second maintainer for when I don't have much time. I will get in contact with you soon.

Thank you @Cretezy and @renefloor for this great effort

If you guys are going to work on anything, please prioritize this issue because it is blocking for many projects.

Thank you again :)

I just updated the dependencies

Was this page helpful?
0 / 5 - 0 ratings

Related issues

gjrjf picture gjrjf  路  4Comments

creativecreatorormaybenot picture creativecreatorormaybenot  路  4Comments

nashfive picture nashfive  路  5Comments

flutteradv picture flutteradv  路  6Comments

gunhansancar picture gunhansancar  路  3Comments