Repository navigation
Fix mark read/unread error and show report-only message bodies - #4
Merged
Merged
Conversation
- Read/unread now use updateRecipientInBatch (READ / AS_UNREAD), as the web app does. createMessageStatusInBatch only accepts DELETED/ARCHIVED, so "READ" failed with "Expected type MessageStatusEnum". - The detail screen reads the message through the inbox entity, like the web app, and shows the server-rendered HTML (`rendered`) and attached reports as field/value cards. Report-only messages (e.g. daily menu) had an empty `content` and showed "(no content)". Falls back to the plain MessageQuery if the new query is rejected. - docs/API.md: document both mutations, the enums, reports and findings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GhkhBACvvZ7yVYXuyKhLad
Live check: a report-only message has null content/rendered, report results with null entityId and CHECK values as JSON arrays; normal messages return rendered == content. Add a test for that shape and mark the findings live-verified in docs/API.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GhkhBACvvZ7yVYXuyKhLad
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Expected type "MessageStatusEnum", found "READ":createMessageStatusInBatchonly acceptsDELETED/ARCHIVED.content.Changes
updateRecipientInBatchwithREAD/AS_UNREAD(+deleteNotification: true,legacyMode: false), as the official web app does. Delete still usescreateMessageStatusInBatch(DELETED).node(entityId).message(id)), requestingrendered(HTML) andreports. The detail screen showsrendered(falling back tocontent) and each report as a card of field/value rows. Falls back to the oldMessageQueryif the new query is rejected.ReportResult.displayValuehandles string, array and JSON-encoded-array values; results are filtered to the inbox entity when a report has per-recipient answers.docs/API.md: documents both mutations, theUpdateRecipientStatus/MessageStatusEnumvalues, the recipient-view query,Report/ReportResultmodels, and the findings in §10.1.Verification
./gradlew testDebugUnitTest lintDebug assembleDebugpasses; new unit tests cover the mutations, the entity query, its fallback and report value shapes.rendered==content). The read/unread mutation itself has not yet been exercised on a live account.🤖 Generated with Claude Code
https://claude.ai/code/session_01GhkhBACvvZ7yVYXuyKhLad
Generated by Claude Code