A failed save still shows the event as saved #43
Labels
No labels
bug
chore
data
feature
frontend
good first issue
intermediate
needs/docs
needs/research
needs/upstream
type/bug
type/external
type/feature
type/refactor
urgency
high
urgency
immediate
urgency
low
urgency
medium
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ScottyLabs/cal#43
Loading…
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?
What's wrong
Saving or unsaving an event updates the UI first and never undoes it if the request fails. Saves fail often right now (see "Saving an event returns 500 for a second user, a repeat save, or no google_event_id"), so users see events as saved that are not stored.
How to reproduce
/api/events/user_saved_events.Expected
If the request fails, the saved state goes back to what it was and the user sees a short error.
Where to look
web/src/context/EventStateContext.tsx:toggleAddedupdatessavedEventIdsbefore the request, and thecatchonly logs.Done when
savedEventIdsis restored to its previous value