fix(webmail): populate reply recipients and subject - #766
Open
luckycrm wants to merge 1 commit into
Open
Conversation
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
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.
Summary
Fixes webmail reply and reply-all composers so recipient chips and the reply subject are initialized from the selected message.
Motivation
The existing reply effect computed recipient arrays but discarded them, while the shared email composer hid the subject whenever a reply ID was present. As a result, replies could open without usable recipients and without a visible or sent subject.
Related issue
None — this is a focused bug fix, which
CONTRIBUTING.mdpermits as a direct pull request.Changes
Verification
bun run --cwd apps/email/client lintcannot start on the upstream checkout because the existingeslint.config.tsimports missing package@zero/eslint-config.The two new files pass scoped Prettier checks. The two existing client files retain their upstream formatting to avoid an unrelated whole-file reformat.
Screenshots
Not applicable; this restores existing reply fields and data flow.
Checklist
bun run test, relevant lint/typechecks, andbun formatpass locally (upstream/environment blockers documented above; relevant tests and builds pass).