Open danpastori opened 6 years ago
We have a flag for incrementing the count on click. This doesn't update the storage so if I refresh the page my click isn't stored.
It can be kind of misleading when I see an increment, refresh the page and it isn't there.
Update the storage if increment is set.
Refreshing the page will show the new share.
If I click and didn't share, then the number will be wrong and won't correct itself until the cache expires.
Let me know your thoughts on this and we can find a way to resolve this issue!
I'd say no on this since the increment assumes the share took place. It would get confusing if we're manipulating the source data. Perhaps what we could do is invalidate the cache for that URL/network on click?
Problem
We have a flag for incrementing the count on click. This doesn't update the storage so if I refresh the page my click isn't stored.
Rationale
It can be kind of misleading when I see an increment, refresh the page and it isn't there.
Solution
Update the storage if increment is set.
Pros of Solution:
Refreshing the page will show the new share.
Cons of Solution:
If I click and didn't share, then the number will be wrong and won't correct itself until the cache expires.
Let me know your thoughts on this and we can find a way to resolve this issue!