A proper solution will see the payload flow abstracted frp-style into a stream of payloads over time and just model the flow of time declaratively and without managing state instead of this horribleness.
Type of change
[ ] Bug fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Description of the change
We were doing this through the
ConnectivityManager
, which was removed yesterday.This adds the suspension back with the main goal of keeping this behavior for the next release.
A proper solution will come when https://github.com/rollbar/rollbar-flutter/issues/70 is addressed.
A proper solution will see the payload flow abstracted frp-style into a stream of payloads over time and just model the flow of time declaratively and without managing state instead of this horribleness.
Type of change
Related issues
Checklists
Development
Code review