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

   ### Which Issue(s) This PR Fixes
   
   Fixes #7183
   
   ### Brief Description
   
   In demo mode, the consumer-group form and CSV validator both pass 
`deliveryOrderType`, but `createConsumerGroup` reconstructs the stored row 
without it. The group is created successfully while its selected FIFO order 
disappears from subsequent reads and CSV exports.
   
   Preserve that optional field in the mock row. This is demo metadata fidelity 
only; live provider/API behavior is unchanged. Both supported order values and 
the bundled FIFO fixture are covered in one fix.
   
   ### How Did You Test This Change?
   
   - Added three regressions: create/read for `PARTITON_ORDER` and 
`MESSAGES_ORDER`, plus export of `cg-inventory-sync` from `instance-proxy-1`, 
validated import into `instance-direct-1`, and re-export.
   - With the final tests and pristine production code, all three regressions 
fail for the missing order value.
   - Final related suite: **62 tests across 4 files passed** 
(`consumerService`, `resourceCsvImport`, `download`, `metadata`).
   - Forced TypeScript, changed-file ESLint/Prettier, production build 
including license checks, and `git diff --check` passed.
   - Independent review checked the immutable diff, fixture cleanup, and 
live/mock scope. Full frontend suite was not run locally.
   
   Related provider-side fixes (#4839, #5950, #6945) do not cover this mock 
storage path; CSV canonicalization (#2458) already preserves the input before 
this point.
   
   ### Checklist
   
   - [x] One coherent change; unrelated modifications are not bundled in
   - [x] Conventional Commit subject
   - [x] Regression tests added, with test names ending in `Test`
   - [x] No new UI text or translation keys
   - [x] Existing ASF headers retained; no new source files
   - [x] No public API or documentation contract change
   


-- 
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