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

   ### Which Issue(s) This PR Fixes
   
   - Resubmission of #1928 (closed during the August branch-rebase sweep, with 
an invitation to resubmit against the current branch). Original report: #1927, 
closed as not planned — the defect is still present on the current 
`rocketmq-studio` tip.
   
   ### Brief Description
   
   In mock mode, `deleteAclRule()` / `deleteAclUser()` treated a missing record 
as **success** (no splice, silent return), while the server answers `404 ACL 
rule not found: <id>` / `404 ACL user not found: <id>` for the same case 
(`AclService.deleteRule` / `deleteUser`). Stale rows in the mock store 
therefore produced false success feedback that the real backend never gives.
   
   Align the mock with the server contract — throw for unknown ids with the 
same message the server uses — and verify failed deletes leave both mock 
collections unchanged.
   
   ### How Did You Test This Change?
   
   ```text
   $ cd web && npx vitest run src/services/aclService.test.ts
    Test Files  1 passed (1)
         Tests  9 passed (9)
   $ npx eslint src/services/aclService.ts src/services/aclService.test.ts   # 
clean
   ```
   
   ### Checklist
   
   - [x] One coherent change; unrelated modifications are not bundled in
   - [x] Commit subject follows Conventional Commits
   - [x] Tests added or updated for non-trivial changes
   - [x] New UI text has both Chinese and English entries under `web/src/i18n/` 
(no new UI text)
   - [x] Architecture constraints stay green (frontend mock layer only)
   - [x] New source files carry the ASF license header (no new files)
   - [x] Documentation touched where behaviour changed (mock now matches the 
server's 404 contract)
   


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