You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fire message update state sync events for attachments that are loaded later (#96)
* -
* Update DatabaseTickWaits.swift
* -
* -
* Rename attachmentRowIDs → attachmentLoadMessageRowIDs
The local in resolvePendingMessageHydrationChanges held message ROWIDs
(passed in as forMessageRowIDs), not attachment ROWIDs; rename so the
name matches what's actually inside.
Generated with [Indent](https://indent.com)
Co-Authored-By: KishanBagaria <KishanBagaria@users.noreply.github.com>
* Update MappedDatabaseRows.swift
---------
Co-authored-by: indent[bot] <216979840+indent[bot]@users.noreply.github.com>
Co-authored-by: KishanBagaria <KishanBagaria@users.noreply.github.com>
Copy file name to clipboardExpand all lines: todos.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,7 @@
17
17
-[ ] separate `UserDefaults` somehow so that CLI and other consumers don't share the prefs
18
18
-[ ] user manually killing the messages.app causes cli to not detect that ("Domain=NSOSStatusErrorDomain Code=-600 "procNotFound: no eligible process with specified descriptor"")
19
19
-[ ] when scheduled messages are actually sent, send a message update event
20
+
-[ ] surface terminal-failure attachment state so a failed/rejected download clears the loading spinner. Today `loading = transferState != .finished` (`MessageMapper+Attachments.swift:26`), so error/recoverableError/rejected (states 6/7/8, `Attachment.swift:31-33`) read as `loading: true` forever; `PlatformSDK.Attachment` (`PlatformSDKAttachment.swift:26`) has no failed flag. After the EventWatcher hydration path stops polling failed transfers, the last emitted state still says loading, so the consumer spins indefinitely. Needs: a failed/error field on the attachment type + mapper wiring + EventWatcher emitting it on terminal failure + consumer-side rendering. The EventWatcher hydration path already drops terminally-failed candidates via `IMFileTransferState.isTerminalFailure`.
20
21
-[ ] perhaps move PlatformSDK to <https://github.com/TextsHQ/platform-sdk>
0 commit comments