Maybe I'm wrong, but if developer specifies offlineOnly mutation then this implies that this mutation will fail when offline.
The same as it could fail with timeout. Developers will need to handle those cases in their UI component (render method) to render proper response. Adding additional callback not only making this less complex but it will mean that they will need to duplicate the handlers for offline only mutations and other network errors that can still happen?
This listener will be quite hacky to build because it will need to follow error strategy that users sets for mutation and hook into rendering logic. |
|
