Requests Disappear when Prayed #26
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: bit-badger/myPrayerJournal#26
Loading…
Reference in New Issue
Block a user
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?
On different devices, requests are disappearing rather than going to the bottom of the journal. I suspect this is due to time differences between the device and the server. Modify the web app to send the timestamp along with actions such as "Prayed" or "Updated", and use that instead of taking the value of "now" from the server.
this will be part of v2
The more I thought about this, taking the client's incorrect time is the wrong solution. Rather than using the time from the client, zero out
showAfter
server-side instead for immediately recurring requests. This will move them to the bottom of the journal (sorted byasOf
desc) and will not trigger the issues that setting it to the current date/time does. Non-immediate recurrence requests should disappear until their recurrence time comes back around, and still will, because theirshowAfter
will be computed based on their recurrence.Fixed in v2