Open prabhu43 opened 4 years ago
@ColinEberhardt Let me know which solution is preferable. I can fix this issue.
Any update on this one?
I opened another issue probably related to this one due to the introduction of clap-limit-exceeded
Here is the link: https://github.com/ColinEberhardt/applause-button/issues/69
Thanks for such a great job @ColinEberhardt ❤️
Thanks for the suggestions - this is a tricky issue, and one that always has an element of compromise. I've made a recent update that works as follows:
clap-count-exceeded
state so that it is visible to the user https://github.com/ColinEberhardt/applause-button/commit/7d346ef4aecbc41db91ace1b923b6cfaad0b97d9clap-count-exceeded
style is applied, and the clap count reset to the server-side value https://github.com/ColinEberhardt/applause-button/commit/eed48b80cd97bf36a9e5f9450757e6540881bbefThis does result in some behaviour that users might find unexpected:
@ColinEberhardt thanks for taking care of this! Amazing job! ❤️
Once a user clap for second time after page refresh, It increments the count in UI. But the update api call does not increase the count as the clap limit exceeded for the user from that IP, it returns the same old value for clap count.
Expected:
If the clap limit exceeded for the user(source ip), disable the button on initialisation(page refresh)
Solutions: