unbridled-41 opened a new pull request, #5952:
URL: https://github.com/apache/rocketmq-dashboard/pull/5952

   ### Which Issue(s) This PR Fixes
   
   Fixes #5951
   
   ### Problem / Evidence
   
   ```tsx
   // CloudCredentialTab (before)
   { title: t('settings.createdAt'), dataIndex: 'gmtCreate', key: 'gmtCreate' },
   ```
   
   The API serializes the zoneless `LocalDateTime`, so the cell read 
`2026-08-18T10:00:00` - the only timestamp in the app that never reaches a 
formatter (UserManagement.tsx: `formatUtcDateTime`, `pages/instance/index.tsx`: 
`formatDateTime`, `pages/instance/acl.tsx`: `formatDate`):
   
   ```
   CloudCredentialTab: formats the created timestamp instead of printing the 
raw wire value
   AssertionError: expected document not to contain element, found <td
   ```
   
   ### Root cause / Fix
   
   A missing `render` on the column. `CloudCredentialService` stamps the field 
with the server clock like the rest of the metadata rows, so render it through 
the same `formatDateTime` the sibling inventory tables use, with `-` for an 
absent value.
   
   ### Priority and scoring
   
   **PRIORITY 45** — impact 12/40 (an unformatted timestamp in an audit 
column), blast radius 8/20 (one table), reproducibility 18/20 (deterministic, 
pinned by the new test), maintenance value 0/20.
   
   **FIX_CONFIDENCE 90** — one column renderer, with three sibling precedents.
   
   ### Tests
   
   `cd web && npx vitest run 
src/pages/settings/__tests__/CloudCredentialTab.test.tsx` -> `Tests 12 passed`.
   
   | Test | Before | After |
   |---|---|---|
   | `formats the created timestamp instead of printing the raw wire value` | 
FAIL (`found <td`) | PASS |
   
   `npx eslint` reports no errors; `npx tsc -b` passes.
   
   ### Risk
   
   None beyond the cell's text; no test depended on the raw value.


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