We don't SWR to automatically revalidate /api/account data that has been locally mutated (e.g. when the user selects subscriptions) but not yet updated server-side (e.g. the user hasn't yet clicked the "Save subscriptions" button).
The current behavior (of SWR revalidating even when local mutations haven't been saved) results in the clearing of subscription selections whenever the user switches tabs (which triggers SWR's automatic revalidation):
This is a high-priority bug over at
tutorbookapp/tutorbookas well:We don't SWR to automatically revalidate
/api/accountdata that has been locally mutated (e.g. when the user selects subscriptions) but not yet updated server-side (e.g. the user hasn't yet clicked the "Save subscriptions" button).The current behavior (of SWR revalidating even when local mutations haven't been saved) results in the clearing of subscription selections whenever the user switches tabs (which triggers SWR's automatic revalidation):
https://user-images.githubusercontent.com/20798889/117685573-e9143f00-b16a-11eb-9582-b979e097d432.mov