🎨 Added Preview tab to welcome email editor#27399
Merged
cmraible merged 14 commits intoApr 22, 2026
Merged
Conversation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughAdds end-to-end support for automated welcome-email previews: new API types and a POST preview mutation hook; a useWelcomeEmailPreview hook that validates drafts, handles concurrency, processes HTML, and maps errors; a WelcomeEmailPreviewFrame component that renders and height-syncs preview HTML in an iframe; welcome-email validation utilities; modal UI updated with edit/preview modes and subject override; Koenig editor typography adjustments; Playwright page helper locators for preview mode; and new/updated unit, acceptance, and e2e tests covering preview behaviors. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
cmraible
force-pushed
the
chris-ny-1228-add-the-frontend-editpreview-toggle-to-the-welcome-email
branch
2 times, most recently
from
b67218c to
2fc597d
Compare
Base automatically changed from
chris-ny-1227-add-the-backend-api-endpoint-to-preview-a-welcome-email
to
main
April 15, 2026 19:23
cmraible
changed the title
cmraible
force-pushed
the
chris-ny-1228-add-the-frontend-editpreview-toggle-to-the-welcome-email
branch
2 times, most recently
from
0a0517c to
137dc14
Compare
cmraible
force-pushed
the
chris-ny-1228-add-the-frontend-editpreview-toggle-to-the-welcome-email
branch
from
137dc14 to
6654797
Compare
troyciesco
reviewed
Apr 16, 2026
Contributor
E2E Tests FailedTo view the Playwright test report locally, run: REPORT_DIR=$(mktemp -d) && gh run download 24520623759 -n playwright-report -D "$REPORT_DIR" && npx playwright show-report "$REPORT_DIR" |
cmraible
commented
Apr 16, 2026
cmraible
commented
Apr 16, 2026
cmraible
force-pushed
the
chris-ny-1228-add-the-frontend-editpreview-toggle-to-the-welcome-email
branch
from
3c4a7d2 to
b7034f5
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (3)
e2e/helpers/pages/admin/settings/sections/member-welcome-emails-section.ts (1)
89-90: AliasedmodalSubjectInputonly works in preview mode.
modalSubjectInputnow points at the preview-onlywelcome-email-preview-subjectinput (which is unmounted in edit mode). Any existing or future callers that interact withmodalSubjectInputwithout first switching to preview mode will hit a hidden locator. Consider either removing the alias and forcing callers to usemodalPreviewSubjectInputexplicitly (clearer intent), or documenting the mode requirement on this field.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@e2e/helpers/pages/admin/settings/sections/member-welcome-emails-section.ts` around lines 89 - 90, The aliasing of modalSubjectInput to the preview-only locator welcome-email-preview-subject causes hidden-locator errors in edit mode; change modalSubjectInput so it does not point at the preview-only element — either remove the alias and require callers to use modalPreviewSubjectInput explicitly, or make modalSubjectInput switch its underlying locator based on mode (preview vs edit) by selecting the preview locator (welcome-email-preview-subject) only when preview mode is active; update any callers of modalSubjectInput to use modalPreviewSubjectInput or to ensure the modal is in preview mode before interacting.apps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-modal.tsx (1)
105-105:previewSubjectOverrideappears redundant.On every keystroke in the preview subject field (Line 296-300), both
previewSubjectOverrideandformState.subjectare set to the same value, and on mode transitions the override is reset tonull(Lines 181, 185). Since the two values are always in sync after any edit and the displayed value ispreviewSubjectOverride ?? formState.subject, the override never changes the rendered subject. Consider removing the extra state and reading/writingformState.subjectdirectly — fewer moving parts and no risk of the two drifting.Proposed simplification
- const [previewSubjectOverride, setPreviewSubjectOverride] = useState<string | null>(null); @@ - const handleModeChange = useCallback((nextMode: PreviewMode) => { - setMode(nextMode); - - if (nextMode === 'preview') { - setPreviewSubjectOverride(null); - enterPreview(formState); - } else { - setShowTestDropdown(false); - setPreviewSubjectOverride(null); - exitPreview(); - } - }, [enterPreview, exitPreview, formState]); + const handleModeChange = useCallback((nextMode: PreviewMode) => { + setMode(nextMode); + + if (nextMode === 'preview') { + enterPreview(formState); + } else { + setShowTestDropdown(false); + exitPreview(); + } + }, [enterPreview, exitPreview, formState]); @@ - value={previewSubjectOverride ?? formState.subject} - onChange={(e) => { - const nextSubject = e.target.value; - setPreviewSubjectOverride(nextSubject); - updateForm(state => ({...state, subject: nextSubject})); - }} + value={formState.subject} + onChange={e => updateForm(state => ({...state, subject: e.target.value}))}Also applies to: 177-188, 292-301
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-modal.tsx` at line 105, Remove the redundant previewSubjectOverride state and its setter (previewSubjectOverride, setPreviewSubjectOverride) and use formState.subject everywhere instead: update the subject input change handler (currently setting both previewSubjectOverride and formState.subject) to only update formState.subject, remove any code that resets previewSubjectOverride on mode transitions, and change the displayed subject expression from previewSubjectOverride ?? formState.subject to just formState.subject; ensure any references to setPreviewSubjectOverride are deleted and tests/handlers that relied on the override now read/write formState.subject directly.apps/admin-x-settings/test/acceptance/membership/member-welcome-emails.test.ts (1)
284-285: Replace deprecatedLocator.type()withpressSequentially().
locator.type()is deprecated in Playwright 1.59; usepressSequentially()for character-by-character input instead.Proposed change
- await previewSubject.press('End'); - await previewSubject.type('!'); + await previewSubject.press('End'); + await previewSubject.pressSequentially('!');🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/admin-x-settings/test/acceptance/membership/member-welcome-emails.test.ts` around lines 284 - 285, Replace the deprecated locator.type call with pressSequentially: locate the previewSubject.type('!') call and change it to use previewSubject.pressSequentially with an array of character strings (e.g. ['!']) so the input is sent character-by-character; keep the existing previewSubject.press('End') as-is and await the new pressSequentially promise to ensure ordering.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@e2e/tests/admin/settings/member-welcome-emails.test.ts`:
- Around line 188-199: The test currently waits for the preview POST
(previewResponse) before changing the subject, so subject edits may not be
included; after clicking modalPreviewTab and before asserting the preview,
trigger and await the request caused by the subject edit: fill modalSubjectInput
with customSubject and create a new waitForResponse that looks for a POST to
'/ghost/api/admin/automated_emails/' containing '/preview/' whose
response/request body includes customSubject (or assert the returned
JSON/response text contains customSubject), then await that response and finally
assert modalPreviewSubjectInput has customSubject; use the existing symbols
previewResponse/modalPreviewTab/modalSubjectInput/modalPreviewSubjectInput/customSubject
to locate and implement this change.
- Line 179: Rename the test titles passed to test(...) in
e2e/tests/admin/settings/member-welcome-emails.test.ts to follow the lowercase
"what is tested - expected outcome" convention; specifically change the string
"free welcome email preview renders edited subject and body" to "free welcome
email preview - renders edited subject and body" (and apply the same pattern to
the other test around the same block referenced in the review) so all test
descriptions use the required lowercase hyphenated format.
- Line 201: The test is using a CSS body selector via
welcomeEmailsSection.modalPreviewFrame.locator('body'); remove the CSS selector
and assert the text directly on the frame locator instead: stop calling
locator('body') and call the frame locator
(welcomeEmailsSection.modalPreviewFrame) in the expect assertion to verify it
contains the customBody text (use the frame locator's semantic text assertion,
e.g., the toContainText-style assertion).
- Around line 210-254: The test currently mutates the welcome email and only
restores the subject; capture the original welcome email object before any
modifications (call getFreeWelcomeEmail(page) into e.g.
originalFreeWelcomeEmail) and in the finally block call
restoreWelcomeEmail(page, originalFreeWelcomeEmail) to restore the entire record
(subject, body, status, etc.) instead of only resetting the subject to
DEFAULT_FREE_WELCOME_EMAIL_SUBJECT; locate usages around welcomeEmailsSection,
getFreeWelcomeEmail, and restoreWelcomeEmail to implement this change.
---
Nitpick comments:
In
`@apps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-modal.tsx`:
- Line 105: Remove the redundant previewSubjectOverride state and its setter
(previewSubjectOverride, setPreviewSubjectOverride) and use formState.subject
everywhere instead: update the subject input change handler (currently setting
both previewSubjectOverride and formState.subject) to only update
formState.subject, remove any code that resets previewSubjectOverride on mode
transitions, and change the displayed subject expression from
previewSubjectOverride ?? formState.subject to just formState.subject; ensure
any references to setPreviewSubjectOverride are deleted and tests/handlers that
relied on the override now read/write formState.subject directly.
In
`@apps/admin-x-settings/test/acceptance/membership/member-welcome-emails.test.ts`:
- Around line 284-285: Replace the deprecated locator.type call with
pressSequentially: locate the previewSubject.type('!') call and change it to use
previewSubject.pressSequentially with an array of character strings (e.g. ['!'])
so the input is sent character-by-character; keep the existing
previewSubject.press('End') as-is and await the new pressSequentially promise to
ensure ordering.
In `@e2e/helpers/pages/admin/settings/sections/member-welcome-emails-section.ts`:
- Around line 89-90: The aliasing of modalSubjectInput to the preview-only
locator welcome-email-preview-subject causes hidden-locator errors in edit mode;
change modalSubjectInput so it does not point at the preview-only element —
either remove the alias and require callers to use modalPreviewSubjectInput
explicitly, or make modalSubjectInput switch its underlying locator based on
mode (preview vs edit) by selecting the preview locator
(welcome-email-preview-subject) only when preview mode is active; update any
callers of modalSubjectInput to use modalPreviewSubjectInput or to ensure the
modal is in preview mode before interacting.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 18fa7537-a16e-4dad-80d9-cf154c08df63
📒 Files selected for processing (10)
apps/admin-x-framework/src/api/automated-emails.tsapps/admin-x-settings/src/components/settings/membership/member-emails/member-email-editor.tsxapps/admin-x-settings/src/components/settings/membership/member-emails/use-welcome-email-preview.tsapps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-modal.tsxapps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-preview-frame.tsxapps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-validation.tsapps/admin-x-settings/test/acceptance/membership/member-welcome-emails.test.tsapps/admin-x-settings/test/unit/hooks/use-welcome-email-preview.test.tsxe2e/helpers/pages/admin/settings/sections/member-welcome-emails-section.tse2e/tests/admin/settings/member-welcome-emails.test.ts
cmraible
commented
Apr 21, 2026
troyciesco
approved these changes
Apr 21, 2026
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (1)
e2e/tests/admin/settings/member-welcome-emails.test.ts (1)
225-226: Replace deprecatedtype()withfill().
Locator.type()is deprecated in Playwright and should be replaced withfill()for form-filling scenarios. This is faster and directly triggers input events. Since you're setting the final value of the input,fill()is appropriate here.♻️ Suggested change
- await welcomeEmailsSection.modalSubjectInput.press('End'); - await welcomeEmailsSection.modalSubjectInput.type('!'); + await welcomeEmailsSection.modalSubjectInput.fill(templatedSubjectWithSuffix);🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@e2e/tests/admin/settings/member-welcome-emails.test.ts` around lines 225 - 226, The test currently uses the deprecated Locator.type() on welcomeEmailsSection.modalSubjectInput to append a '!' after pressing End; replace this with using inputValue() to read the current value and then fill() with the new value (e.g., read welcomeEmailsSection.modalSubjectInput.inputValue(), concatenate '!' and call welcomeEmailsSection.modalSubjectInput.fill(newValue)) so the final input is set via fill() instead of the deprecated type().
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@e2e/tests/admin/settings/member-welcome-emails.test.ts`:
- Around line 225-226: The test currently uses the deprecated Locator.type() on
welcomeEmailsSection.modalSubjectInput to append a '!' after pressing End;
replace this with using inputValue() to read the current value and then fill()
with the new value (e.g., read
welcomeEmailsSection.modalSubjectInput.inputValue(), concatenate '!' and call
welcomeEmailsSection.modalSubjectInput.fill(newValue)) so the final input is set
via fill() instead of the deprecated type().
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 476631b3-8ffd-4285-a126-1603831e534c
📒 Files selected for processing (1)
e2e/tests/admin/settings/member-welcome-emails.test.ts
Contributor
E2E Tests FailedTo view the Playwright test report locally, run: REPORT_DIR=$(mktemp -d) && gh run download 24740401196 -n playwright-report -D "$REPORT_DIR" && npx playwright show-report "$REPORT_DIR" |
1 similar comment
Contributor
E2E Tests FailedTo view the Playwright test report locally, run: REPORT_DIR=$(mktemp -d) && gh run download 24740401196 -n playwright-report -D "$REPORT_DIR" && npx playwright show-report "$REPORT_DIR" |
This lets staff switch between editing and previewing welcome emails without saving first, keeps the preview synced with unsaved changes, and adds focused coverage for preview rendering, stale-response handling, and browser behavior.
This aligns edit and preview behavior with the new workflow so content editing, preview framing, and tab affordances are consistent.
ref https://linear.app/ghost/issue/NY-1228/ The modal intentionally moved subject, sender, and test controls into preview mode, so the acceptance and E2E coverage needed to follow the new interaction flow and explicitly enable delivery before asserting sent welcome emails.
ref https://linear.app/ghost/issue/NY-1228/ The preview frame was using two effects to reset state and register the same cleanup. Consolidating them keeps the lifecycle logic in one place and makes the component easier to follow during review.
The preview hook and its validation helper are only used by the welcome email modal, so keeping them under src/hooks made the feature harder to follow and forced the validation helper to be exported from the hook file just to share it with the modal.
The preview hook did not need stable callback identities for its internal control flow, and the extra wrapper around entering preview only added indirection. Simplifying these functions keeps the hook easier to read without changing behavior.
Sonar flagged the nested ternary used to derive previewFrameState, and rewriting it as a small local branch makes the returned state easier to scan without changing behavior.
Sonar flagged the legacy assert import, and the test still referenced the hook's pre-move path. Updating both imports keeps the test aligned with current Node import conventions and the colocated hook location.
The preview frame still referenced the old top-level hook path after the preview logic was moved into the member-emails feature folder. Updating the type import fixes the admin-x-settings TypeScript build without changing runtime behavior.
ref https://linear.app/tryghost/issue/NY-1228/ This locks down the preview-edit-save flow in a real browser and restores the default subject after the test so later welcome email specs stay isolated.
ref https://linear.app/tryghost/issue/NY-1228/ This aligns the preview tests with the local E2E naming rules and removes the non-semantic iframe body selector that CodeRabbit flagged.
ref https://linear.app/tryghost/issue/NY-1228/ This removes memoization that was only there to satisfy hook dependency management and keeps the preview frame logic easier to follow without changing behavior.
cmraible
force-pushed
the
chris-ny-1228-add-the-frontend-editpreview-toggle-to-the-welcome-email
branch
from
2413356 to
229c83b
Compare
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@apps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-modal.tsx`:
- Around line 290-301: The preview subject field (TextField using
value={previewSubjectOverride ?? formState.subject} and onChange that calls
setPreviewSubjectOverride/updateForm) does not show validation errors because
the modal only renders errors.lexical; update the preview subject area to also
render errors.subject using the same Hint component pattern used for lexical
errors (the Hint component near the lexical error at line 335) so that when
errors.subject exists it is displayed inline next to the preview subject field.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 4fa491ab-fb1c-48fe-8275-ba82a640395e
📒 Files selected for processing (10)
apps/admin-x-framework/src/api/automated-emails.tsapps/admin-x-settings/src/components/settings/membership/member-emails/member-email-editor.tsxapps/admin-x-settings/src/components/settings/membership/member-emails/use-welcome-email-preview.tsapps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-modal.tsxapps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-preview-frame.tsxapps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-validation.tsapps/admin-x-settings/test/acceptance/membership/member-welcome-emails.test.tsapps/admin-x-settings/test/unit/hooks/use-welcome-email-preview.test.tsxe2e/helpers/pages/admin/settings/sections/member-welcome-emails-section.tse2e/tests/admin/settings/member-welcome-emails.test.ts
✅ Files skipped from review due to trivial changes (3)
- apps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-validation.ts
- apps/admin-x-settings/src/components/settings/membership/member-emails/member-email-editor.tsx
- apps/admin-x-settings/test/acceptance/membership/member-welcome-emails.test.ts
🚧 Files skipped from review as they are similar to previous changes (4)
- apps/admin-x-framework/src/api/automated-emails.ts
- e2e/helpers/pages/admin/settings/sections/member-welcome-emails-section.ts
- apps/admin-x-settings/test/unit/hooks/use-welcome-email-preview.test.tsx
- apps/admin-x-settings/src/components/settings/membership/member-emails/use-welcome-email-preview.ts
ref https://linear.app/tryghost/issue/NY-1228/ Preview mode keeps the subject field editable, so subject validation needs to stay visible there as well. This shows the existing inline error next to the preview subject input instead of only rendering lexical validation below the editor.
|
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (1)
apps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-modal.tsx (1)
105-105:previewSubjectOverrideappears redundant withformState.subject.The TextField's
onChangesets bothsetPreviewSubjectOverride(nextSubject)andupdateForm(state => ({...state, subject: nextSubject}))to the same value, and on every mode changepreviewSubjectOverrideis reset tonull(falling back toformState.subject). Since the subject cannot be edited anywhere else while in preview (the editor pane only receivesvalue={formState.lexical}), the override andformState.subjectcan never diverge, so the override serves no user-visible purpose and just adds a second source of truth to keep in sync.Consider dropping the override state and binding directly to
formState.subject:♻️ Proposed simplification
- const [previewSubjectOverride, setPreviewSubjectOverride] = useState<string | null>(null); @@ - if (nextMode === 'preview') { - setPreviewSubjectOverride(null); - enterPreview(formState); - } else { - setShowTestDropdown(false); - setPreviewSubjectOverride(null); - exitPreview(); - } + if (nextMode === 'preview') { + enterPreview(formState); + } else { + setShowTestDropdown(false); + exitPreview(); + } @@ - <TextField - className='w-full' - data-testid='welcome-email-preview-subject' - value={previewSubjectOverride ?? formState.subject} - onChange={(e) => { - const nextSubject = e.target.value; - setPreviewSubjectOverride(nextSubject); - updateForm(state => ({...state, subject: nextSubject})); - }} - /> + <TextField + className='w-full' + data-testid='welcome-email-preview-subject' + value={formState.subject} + onChange={e => updateForm(state => ({...state, subject: e.target.value}))} + />If the intent is to later allow previewing with a subject that is not committed to the draft until save, that plan isn't realized today and the two are always kept in lockstep.
Also applies to: 295-301
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-modal.tsx` at line 105, Remove the redundant previewSubjectOverride state and its setter (previewSubjectOverride, setPreviewSubjectOverride) and instead read/write the subject directly from formState.subject via updateForm; update the TextField onChange to only call updateForm(state => ({...state, subject: nextSubject})), remove any code that resets previewSubjectOverride on mode changes, and replace any preview fallbacks that read previewSubjectOverride with formState.subject so there is a single source of truth for the subject.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In
`@apps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-modal.tsx`:
- Line 105: Remove the redundant previewSubjectOverride state and its setter
(previewSubjectOverride, setPreviewSubjectOverride) and instead read/write the
subject directly from formState.subject via updateForm; update the TextField
onChange to only call updateForm(state => ({...state, subject: nextSubject})),
remove any code that resets previewSubjectOverride on mode changes, and replace
any preview fallbacks that read previewSubjectOverride with formState.subject so
there is a single source of truth for the subject.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 46df10c7-31e5-421a-bdb2-039ed8e77b32
📒 Files selected for processing (1)
apps/admin-x-settings/src/components/settings/membership/member-emails/welcome-email-modal.tsx
cmraible
deleted the
chris-ny-1228-add-the-frontend-editpreview-toggle-to-the-welcome-email
branch
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
4 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.
ref https://linear.app/ghost/issue/NY-1228/add-the-frontend-editpreview-toggle-to-the-welcome-email-edit-modal
What this changes
Edit/Previewtoggle to the welcome email modal in AdminWhy
The welcome email editor previously only exposed the raw editing experience, which made it harder to verify the final email output before saving. This change adds an in-context preview flow so admins can check both copy and rendered layout while keeping their draft intact.
Implementation notes
usePreviewWelcomeEmailmutation and preview response types inadmin-x-framework