The documentation about offline entry would not say something about altering the consequences of offline writes, solely offline reads. The code you are exhibiting subsequently solely impacts the learn habits. Write habits stays the identical (that means that offline writes proceed to build up till the app is ready to come again on-line and the queue is ready to clear).
Even in the event you disable the offline cache completely, the documentation nonetheless clearly states:
Write operations are queued till community entry is re-enabled.
Consider it this manner: It will be critically unhealthy for any app to idiot the top consumer into considering their modifications had been dedicated, just for them to come back again later and understand that every part was truly misplaced. Disabling write persistence would threat exactly this example, which is why it isn’t an possibility.