mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #1455] Deleting history UI bug #471
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#471
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @IshaGupta18 on GitHub (Jan 31, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1455
Describe the bug
History is deleted on clicking on clear all, but change appears only after refreshing the page ie doesn't happen asynchronously and the page has to be updated to see the cleared history.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
The history tab should be cleared as soon as "Clear All" is clicked (asynchronously).
Screenshots

@liyasthomas commented on GitHub (Jan 31, 2021):
Ahh, this looks like a minor UX delay. I mean, yes UI should be updated instantaneously.
As of now, what we're doing is - when you click "Clear All", we loop every entry in history and delete it. This is the recommended way on deleting all collection entries in Firestore. We can show an instantaneous response here by not waiting for Firebase micro-service to do it's job - but again it'll cause another serious issue. If any error happens with Firebase delete operations - user is left with an incorrect UI response.