Skip to content

Keep unsaved message edit when closing the Concierge side panel - #103950

Merged
Gonals merged 4 commits into
mainfrom
claude-keepEditDraftOnSidePanelClose
Oct 20, 2026
Merged

Gonals merged 4 commits into
mainfrom
claude-keepEditDraftOnSidePanelClose

Conversation

@MelvinBot

@MelvinBot MelvinBot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

On wide web, the Concierge side panel renders a second ReportScreen next to the central report. Both run useClearReportActionDraftsOnReportChange, which calls clearAllReportActionDrafts() on mount and unmount. That function wipes the whole REPORT_ACTIONS_DRAFTS collection. So opening or closing the side panel discarded an unsaved edit in the central chat, and the editor closed.

This PR skips the clearing when the hook runs inside the side panel (useIsInSidePanel()). The central report and SearchMoneyRequestReportPage still discard edit drafts when you leave or switch reports. A unit test covers both cases.

AI checks run locally: the new unit test and SearchMoneyRequestReportPageTest pass, and ESLint, cspell and the React Compiler check pass on the changed files. npm run typecheck fails only on tests/actions/PolicyTest.ts(782,17), which this PR doesn't touch. A browser check couldn't run because the test session failed to sign in.

Fixed Issues

$ #103036
PROPOSAL: #103036 (comment)

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Precondition: Web, with the browser window wider than 1300px. At 1300px or narrower the side panel is a modal, so you can't use the central chat while it's open.

  1. Open any chat other than Concierge. The Help button is hidden in the Concierge chat.
  2. Send a message, for example hello.
  3. Click Help in the chat header. The Concierge side panel opens docked on the right, and the central chat stays usable.
  4. In the central chat, hover over hello, open the context menu and choose Edit comment.
  5. Change the text to hello world, and don't save.
  6. Click Close (the X) in the side panel header.
  7. Verify the inline editor stays open with hello world.
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified any copy / text that was added to the app is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Co-authored-by: mkhutornyi <mkhutornyi@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

The failing typecheck check is unrelated to this PR, so I didn't push a fix.

Analysis: main has a TypeScript error. In tests/actions/PolicyTest.ts:763 and tests/actions/PolicyTest.ts:782, the same duplicateWorkspace call passes personalDetailsByLogins twice. TypeScript reports TS1117: An object literal cannot have multiple properties with the same name.

Evidence: This PR only changes useClearReportActionDraftsOnReportChange.ts and its unit test. It doesn't touch PolicyTest.ts.

Fix: [No QA] Fix ESLint and typecheck failures on main removes the duplicate line. After it merges, merge main into this branch and the check should pass.

ESLint check was still pending when I checked. Check independent approval doesn't block on code changes.


view run

@mkhutornyi

Copy link
Copy Markdown
Contributor

@codex review

@mkhutornyi

Copy link
Copy Markdown
Contributor

@MelvinBot review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-14T02:44:20.208681Z 4adede0 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: d43370acd0

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Fixed the failing checks: I merged main into this branch in 8c9c5e6. typecheck and ESLint check now pass.

Both failures came from main, not from this PR's changes. [No QA] Fix ESLint and typecheck failures on main fixed them and has merged. The merge commit brings in that fix:

  • typecheck: removes the duplicate personalDetailsByLogins key in tests/actions/PolicyTest.ts.
  • ESLint: adds seatbelt entries for the deprecated MenuItemWithTopDescription in MoneyRequestViewReportFields.tsx and MoneyReportView.tsx.

Check independent approval still fails. It will pass after an independent reviewer approves the PR.


view run

@MelvinBot

MelvinBot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor Author

🤖 Web test steps verification results: ✅ pass

The Concierge side panel docks on the right in a wide window, and closing it (or reopening and closing it again) keeps an unsaved inline edit. Switching reports still discards the draft, which matches existing behavior.

After switching reports and back, message shows hello, editor closed

Step Status
Open a non-Concierge chat at 1600px wide; Help button visible in headerDM chat opened; header shows the Help button.
DM chat open with Help button in header
✅
Send message hello; it appears in the chatMessage hello is visible in the chat.
hello message sent in DM
✅
Click Help; Concierge side panel docks on the right and central chat stays usableSide panel rendered as a third column (not a modal) beside the LHN and central chat, which stayed visible and interactive.
Concierge panel docked on the right beside the central chat
✅
Open the context menu on hello and choose Edit comment; inline editor opens with helloThe automation's hover didn't reveal the desktop mini toolbar, so the tester opened the full context menu by clicking the message instead (same menu, lists Edit comment). The inline editor opened with hello.
Inline editor open showing hello
✅
Change text to hello world without savingEditor value read back as hello world.
Editor showing hello world, unsaved
✅
Click Close (X) in the side panel header; editor stays open with hello worldAfter the panel closed, the editor still contained hello world, with Close and Save changes buttons present.
Side panel open, editor showing hello world
Side panel closed, editor still showing hello world
✅
Regression: reopen the side panel via Help and close it again; editor still shows hello worldAfter the reopen and close cycle, the editor still showed hello world.
After reopen and close, editor still shows hello world
✅
Regression: switch to another chat and back; edit draft is discardedAfter switching to Concierge and back, the editor was closed and the message showed the saved text hello.
After switching reports and back, message shows hello, editor closed
✅

view run · view recording

@MelvinBot

Copy link
Copy Markdown
Contributor Author

⏱️ Ran out of time before I could finish. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in #melvinbot-ai.

Run details

@mkhutornyi

Copy link
Copy Markdown
Contributor

@MelvinBot

Unsaved edit in the side panel now survives closing the panel

This early return also skips the cleanup when the side panel closes, so the side panel's own edit draft is kept and the editor reopens with the unsaved text. On every other report, leaving and coming back dismisses the edit.

  1. Web, window wider than 1300px. Open any chat other than Concierge.
  2. Click Help. In the Concierge side panel, send hello.
  3. Hover hello in the side panel and choose Edit comment. Change it to hello world and don't save.
  4. Close the side panel (X), then click Help again.

Expected: The edit is dismissed and hello is shown, as on main.
Actual: The editor is still open with hello world.

@MelvinBot

MelvinBot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor Author

🤖 Web test steps verification results: ❌ fail

I couldn't run the regression checks: the browser automation couldn't put a message into edit mode (hover, plain click, and the Up arrow shortcut all failed), so no step reached the PR's code path and this is not an App failure. From the code, the likely regression is that the side panel now never clears drafts (useClearReportActionDraftsOnReportChange.ts:13-16), so an unsaved edit made inside the Concierge side panel may stay open after you close and reopen the panel, where main discards it. Please check steps 2 and 3 by hand.

Plain click on own message; no context menu or editor appears

Step Status
Wide window: in the docked side panel's Concierge chat, send panel msg and edit it to panel msg edited without savingThe side panel docked at 1600x900 and panel msg was sent, but no automation action opened the context menu or inline editor.
Side panel docked at 1600x900
panel msg sent in the Concierge side panel; no context menu reachable
❌
Wide window: close and reopen the side panel; check whether the unsaved side panel edit is kept (possible regression) or discarded (main behavior)Blocked: step 1 couldn't enter edit mode.
❌
Narrow window (1200px, modal side panel): same close and reopen checkNot run: blocked by the same edit-mode limitation.
❌
Wide window, side panel open: edit a central chat message without saving, switch chats and back; draft is discardedHover, the Up arrow key (the tool typed it as literal text), and plain click on the message all failed to open the editor.
Hover over own message in a room; no toolbar appears
Composer shows literal ArrowUp text instead of a key event
Plain click on own message; no context menu or editor appears
❌

view run · view recording

Co-authored-by: mkhutornyi <mkhutornyi@users.noreply.github.com>
@MelvinBot

MelvinBot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor Author

Good catch, mkhutornyi. I fixed it in 4adede0.

The side panel now clears only its own report's edit draft when it opens, closes, or switches reports (useClearReportActionDraftsOnReportChange.ts:13-19). The draft is cleared through a new clearReportActionDrafts(reportID) helper (Report/index.ts:3844). The result:

  • An unsaved edit in the side panel is dismissed when you close the panel, as on main.
  • An unsaved edit in the central chat still survives opening and closing the panel, which is the original fix.

The unit test now covers both cases. The test, ESLint, and npm run typecheck all pass.

I couldn't check this in the browser. The test session showed a blank page after its onboarding setup failed, so no steps ran. Please run your four steps by hand to confirm.


view run · no recording available

@codecov

codecov Bot commented Oct 14, 2026 •

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
...report/useClearReportActionDraftsOnReportChange.ts 100.00% <100.00%> (ø)
src/libs/actions/Report/index.ts 72.68% <0.00%> (-0.60%) ⬇️
... and 19 files with indirect coverage changes

@mkhutornyi

Copy link
Copy Markdown
Contributor

@MelvinBot add QA Steps, same as OP in the linked issue

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Added the QA Steps to the PR description. They copy the precondition, steps and expected result from [$175] Web - Chat - Unsaved inline edit is discarded when closing the Concierge side panel.

  • Precondition: web, window wider than 1300px
  • Steps 1–6: the issue's Action Performed steps
  • Step 7: the Expected Result, written as a check: the inline editor stays open with hello world

The JS console check is still there. I left the Tests section as it was.


view run

@mkhutornyi

Copy link
Copy Markdown
Contributor

@MelvinBot mark this PR ready for review

@MelvinBot
MelvinBot marked this pull request as ready for review October 14, 2026 02:39
@MelvinBot
MelvinBot requested a review from a team as a code owner October 14, 2026 02:39
@melvin-bot
melvin-bot Bot requested a review from mkhutornyi October 14, 2026 02:39
@MelvinBot

Copy link
Copy Markdown
Contributor Author

🤖 Done. This PR is now ready for review.

The Tests and QA Steps sections still contain the TODO placeholders. Please fill them in before review. You can reuse the steps from the web test run above.


view run

@melvin-bot
melvin-bot Bot requested review from flaviadefaria and removed request for a team October 14, 2026 02:40
@melvin-bot

melvin-bot Bot commented Oct 14, 2026

Copy link
Copy Markdown

@mkhutornyi Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot removed the request for review from a team October 14, 2026 02:40
@mkhutornyi

mkhutornyi commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified any copy / text that was added to the app is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
ios.mp4
iOS: mWeb Safari
msafari.mp4
MacOS: Chrome / Safari
web.mov

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4adede0779

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +16 to +18
return () => {
clearReportActionDrafts(reportID);
};

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Clear drafts from their actual owning report bucket

When the side panel displays a thread and the user edits its surfaced parent action, saveReportActionDraft() stores that draft under the parent report ID rather than the visible thread ID. On close, this cleanup deletes only the thread's bucket, so the parent-action draft survives and reopens the editor when the thread is revisited. Resolve and clear the draft-owning report ID instead of assuming it always equals reportID.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, but I couldn't find a case where this is visible.
Closing with X / back / Esc switches the panel back to the Concierge chat while it slides out, which clears the parent draft.
The only close that skips that is navigating away on narrow screens, and every screen that could show the leftover draft clears it when it opens (the Concierge chat in the panel, or any report in the main view).
So the editor never reopens.

Comment on lines +8 to +26
function useClearReportActionDraftsOnReportChange(reportID: string | undefined) {
const isInSidePanel = useIsInSidePanel();

useEffect(() => {
// The side panel report renders next to the central report, so opening or closing it only discards the side panel report's own edit draft
if (isInSidePanel) {
clearReportActionDrafts(reportID);

return () => {
clearReportActionDrafts(reportID);
};
}

clearAllReportActionDrafts();

return () => {
clearAllReportActionDrafts();
};
}, [reportID]);
}, [reportID, isInSidePanel]);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MelvinBot we should not change mobile web behavior on production.

Suggested change:

function useClearReportActionDraftsOnReportChange(reportID: string | undefined) {
    const isInSidePanel = useIsInSidePanel();
    const {isExtraLargeScreenWidth} = useResponsiveLayout();
    // Only the docked panel sits beside a usable chat, the narrow modal covers it like a new page on native
    const isDockedSidePanel = isInSidePanel && isExtraLargeScreenWidth;

    useEffect(() => {
        if (isDockedSidePanel) {
            clearReportActionDrafts(reportID);

            return () => {
                clearReportActionDrafts(reportID);
            };
        }

        clearAllReportActionDrafts();

        return () => {
            clearAllReportActionDrafts();
        };
    }, [reportID, isDockedSidePanel]);
}

Co-authored-by: mkhutornyi <mkhutornyi@users.noreply.github.com>
@MelvinBot
MelvinBot requested a review from a team as a code owner October 14, 2026 03:17
@melvin-bot
melvin-bot Bot requested review from mkhutornyi and removed request for a team October 14, 2026 03:17
@melvin-bot

melvin-bot Bot commented Oct 14, 2026

Copy link
Copy Markdown

@mkhutornyi Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Done. I applied your suggestion in 9f0e947. Only the docked side panel (isInSidePanel && isExtraLargeScreenWidth) now clears just its own report's drafts. The narrow modal and native keep calling clearAllReportActionDrafts(), as on production.

The unit tests, ESLint, cspell, the React Compiler check and npm run typecheck all pass.


view run

@melvin-bot

melvin-bot Bot commented Oct 14, 2026

Copy link
Copy Markdown

We did not find an internal engineer to review this PR, trying to assign a random engineer to #103036 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@melvin-bot
melvin-bot Bot requested a review from Gonals October 14, 2026 03:21
@Gonals
Gonals merged commit 63633b7 into main Oct 20, 2026
43 of 45 checks passed
@Gonals
Gonals deleted the claude-keepEditDraftOnSidePanelClose branch October 20, 2026 13:41
@github-actions

Copy link
Copy Markdown
Contributor

🚧 Gonals has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/Gonals in version: 9.5.15-1 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

Copy link
Copy Markdown
Contributor Author

No help site update is needed. This bug fix keeps an unsaved message edit when you open or close the Concierge side panel, which is what users already expect, and it doesn't make any help article sentence incorrect.


view run

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.5.15-3 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

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

Labels

Melvin-Test-Android Melvin-Test-Web Triggers Melvin to run the testing steps of the PR on web

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants