Publishing custom cache manager implementation best practices

[nareddyt]

💬 Questions and Help

Background: I extended BaseCacheManager to create a custom cache that uses Firebase Performance to trace HTTP network requests.

Implementation wise, it's very simple: Just like DefaultCacheManager with a custom FileService class that traces requests inside get(...). It uses the firebase_performance sdk to create the traces, just a few lines of code.

I am considering publishing this as a pub package. This would help alleviate some common issues and feature requests for Firebase Performance related to automatic network tracing.

Question: Are there any best practices for publishing a custom cache manager implementation as a pub package? Are there examples of other published cache manager implementations?

Specifically, I'm looking for:

• Package naming convention to imply its builds off of this package
• How to show it works with cached_network_image, or any other package that uses flutter_cache_manager under the hood
• If there is some wiki page that contains all known custom cache implementations that I should add it to

[nareddyt]

Well, I published the package: https://pub.dev/packages/traced_cache_manager

Let me know if there's anything that can be improved. Feel free to close this issue if you have no comments.