zmuxuny opened a new pull request, #7128:
URL: https://github.com/apache/rocketmq-dashboard/pull/7128

   ## Which Issue(s) This PR Fixes
   
   Fixes #7125
   
   ## Summary
   
   The persisted-conversation migration left three live backend entry points 
available in Mock mode: history listing/actions, conversation deep-link 
timeline/attachment, and draft handoff creation/sending. The ordinary composer 
was disabled, but these paths bypassed that boundary.
   
   - Treat the effective conversation id as absent in Mock, so timeline loading 
and active-run attachment stay inactive.
   - Keep history openable with localized guidance instead of mounting its live 
query and mutation controls.
   - Consume a Mock draft into the local composer, preserving its text and 
stripping the route intent without creating a conversation or sending a 
message. Switching to Real and reloading does not silently submit it; manual 
submission still works.
   
   This follows the existing Mock-mode contract. Related #2017/#2018/#2309 used 
the older stream and sessionStorage history; this change covers the later 
persisted-conversation APIs rather than reimplementing those changes.
   
   ## Validation
   
   - Eight new real-AiPage regressions fail on unchanged 
`127c47b06a268cc74224d5f34c56ec7c36ac0d55`: EN/ZH history button and Home 
history intent, active conversation deep link, draft handoff on both route 
shapes, and Mock-to-Real reload/manual submission.
   - `npx vitest run src/pages/ai src/pages/home src/i18n --pool=threads 
--maxWorkers=1`: **28 files, 318 tests passed**. Existing Real-mode history, 
send, and active-run reattachment tests remain green.
   - `npx tsc -b --force`: passed.
   - ESLint and Prettier checks for all five changed files: passed.
   - `git diff --check`: passed.
   
   AI assistance was used for investigation, implementation, and regression 
authoring. The production changes and regression coverage were independently 
reviewed.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to