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

   ## Summary
   
   - **Create Group modal**: the 「订阅组类型」 field was a `Select` offering 
普通/顺序/延迟/事务, and picking 顺序 revealed a second 「顺序类型」 `Select` with a 全局顺序 
option. Delay/transaction are topic-level message types that do not apply to 
consumer groups, and no backend supports a globally ordered group (the cloud 
OpenAPI only accepts Concurrently/Orderly). The field now uses the same 
`Segmented` control as the create-topic modal with only 普通消息/顺序消息 (each with a 
one-line `extra` description), the delivery-order select is gone, and 
`deliveryOrderType` is derived from the chosen type (`PARTITON_ORDER` for FIFO) 
so ordered groups still reach the broker / cloud API as orderly.
   - **Audit page (`/ops/audit`)**: the summary statistic cards sized to their 
content, so the 成功率 card (one extra numerator/denominator line) rendered 134px 
tall next to three 90px siblings. All cards in the summary row and the 
risk-insight statistic row now stretch per row (`Row align="stretch"` + `Card 
style={{ height: '100%' }}`, same pattern as `DashboardTrafficInsights`); 
measured in a real browser before/after: 90/134/90/90 → 134/134/134/134.
   
   ## Test plan
   
   - [x] `ConsumerPage.test.tsx`: the old global-order case rewritten to assert 
the two-option Segmented, the absence of delay/transaction/顺序类型 controls and 
the `PARTITON_ORDER` payload; targeted run 72/72 green
   - [x] `AuditSummaryCards.test.tsx` + `AuditPage.test.tsx` (23) and 
`AuditRiskInsights.test.tsx` (6) green
   - [x] Full gate before commit: `npm run build` (tsc + vite + license check) 
and `npx vitest run` — 167 files / 2037 tests passed
   - [x] Deployed to a test machine and verified in headless Chromium: 
create-group dialog shows the Segmented with two options and no dropdown; audit 
summary row heights equal per visual row


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