tree e72ce9122000df6f01e3132d0fac8839fe367cd2
parent 9309ebe322b0420dd23e3cdc8775bfc80cecc368
author Lasse R.H. Nielsen <lrn@google.com> 1648054946 +0100
committer GitHub <noreply@github.com> 1648054946 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJiO1KiCRBK7hj4Ov3rIwAA39cIAEF17dxh6Ny3k+oShxx4vnEq
 mapYFXnBiVPAwRzwpKsXcXr5Z/FJgrllDDhKXbm7VzfBhMqNuk0BsIf1fOEiOlQX
 5sKDb+GgzbZpuNIHF5fQPdC4alZ0wNN+/tZckpnAgnZJXRGbXDdG+MaKTkcKMBOl
 hhbfNupBi2jh4llye7L1/GZgLfzGdgYfurII+p4Qe0JFT/GuGJgFPNKTw+UO7Diy
 2vtq3p2v1DzY6TuIKf7Zj6vqn1BIfThEmBLwk48lQi9PVK6S2d5mULVm2WRdIEP9
 LMhM782INGf8iMtWCtf4oEVu2cBLrSOYOQ6srwjIa8mWJSDmJweGLu6hJ1MSwCw=
 =9e5G
 -----END PGP SIGNATURE-----
 

Deprecate `AsyncCache.fetchStream`. (#209)

* Deprecate `AsyncCache.fetchStream`.

The feature complicates the `AsyncCache` class, and would be a better fit
for a separate class.
The functionality is not great. Since it returns the "same" stream
each time the cache is queried (until evaluated), it actually
caches all stream events
The invalidation is tricky because the timer doesn't start until
you *listen* to the stream. In practice, people will usually
listen to the stream they fetch.

It also seems that no-one ever used the functionality.
There is no use inside Google, or in [Github](https://github.com/search?q=%22.fetchStream%22+language%3ADart+-filename%3Aasync_cache.dart+-filename%3Aasync_cache_test.dart&type=code),
outside of the package's own tests.

It's a better fit for a separate class, but it also appears to not be used anywhere