Skip to content

Messaging component reference #569

Closed
Closed
Messaging component reference#569
Assignees
vickydve
Labels
Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentatione2eefrontend

Description

@codebestia
codebestia
opened on Aug 27, 2026

Write apps/web/docs/components-messaging.md for src/components/messaging/: MessageThread, InboundMessageRow, EncryptedThumbnail, UnavailableMessagePlaceholder — the components that render the decrypted (or undecryptable) message stream.

Acceptance criteria:

  • Each component documented with props and where it is rendered
  • Documents the states a message row can be in — decrypted, unavailable/pre-link, deleted tombstone, system event, file/image — and which component handles each
  • Explains UnavailableMessagePlaceholder and the distinction it must preserve: "this device legitimately has no envelope" is not the same as "decryption failed"
  • Documents EncryptedThumbnail's decrypt-to-object-URL flow and its cleanup obligation

Activity

  1. codebestia
    added
    documentationImprovements or additions to documentation
    frontend
    e2ee
    on Aug 27, 2026
  2. drips-wave
    added
    Stellar WaveIssues in the Stellar wave program
    on Aug 27, 2026

  3. Marskill65 commented on Aug 27, 2026

    @Marskill65
    Marskill65
    on Aug 27, 2026 – with Drips Wave

    @Marskill65 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hello Maintainer, I’ve reviewed the messaging documentation requirements and understand the need to accurately document both the component responsibilities and message states. I can document each component’s props and rendering location, clearly distinguish decrypted, unavailable, deleted, system, and file/image states, and explain the important difference between a missing envelope and a decryption failure. I’ll also document "EncryptedThumbnail"’s decrypt-to-object-URL lifecycle and cleanup requirements. I’m ready to start immediately and iterate quickly on feedback. Kindly assign this issue to me.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Marskill65 to this issue.

  4. vickydve commented on Aug 30, 2026

    @vickydve
    vickydve
    on Aug 30, 2026 – with Drips Wave
    Contributor

    @vickydve has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hi, I'd like to work on this issue. I'll write apps/web/docs/components-messaging.md for src/components/messaging/ (MessageThread, InboundMessageRow, EncryptedThumbnail, UnavailableMessagePlaceholder), documenting each component's props and where it renders, the possible states of a message row (decrypted, unavailable/pre-link, deleted tombstone, system event, file/image) and which component handles each, the distinction UnavailableMessagePlaceholder must preserve between a legitimately missing envelope and a failed decryption, and EncryptedThumbnail's decrypt-to-object-URL flow and cleanup obligation. I'll verify against the component source before opening a PR.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @vickydve to this issue.

  5. codebestia
    assigned
    vickydve
    on Aug 30, 2026

  6. drips-wave commented on Aug 30, 2026

    @drips-wave
    drips-waveBot
    on Aug 30, 2026 – with Drips Wave

    Congratulations, @vickydve! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

    🧑‍💻 @vickydve: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  7. github-actions commented on Aug 30, 2026

    @github-actions
    github-actionsBot
    on Aug 30, 2026 – with GitHub Actions

    Closed by #596, merged into dev.

  8. github-actions
    closed this as completedon Aug 30, 2026

  9. drips-wave commented on Aug 30, 2026

    @drips-wave
    drips-waveBot
    on Aug 30, 2026 – with Drips Wave

    This issue has been completed by @vickydve as part of the Stellar Wave Program's 8th Wave 🥳

    😎 @vickydve: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentatione2eefrontend

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions