chstercc opened a new pull request, #6928:
URL: https://github.com/apache/rocketmq-dashboard/pull/6928
### Which Issue(s) This PR Fixes
- Fixes #6891
### Brief Description
The topic query, the DLQ export window and the DLQ resend window always send
a full start/end pair, so their pickers have no empty state to clear to. With
the default `allowClear`, the clear (×) control snapped the value back and the
next query/export/resend silently reused the previous window.
Disable the clear control on those three `RangePicker`s
(`allowClear={false}`). Changing the window stays available through the picker
itself.
### How Did You Test This Change?
- `cd web && npx vitest run
src/pages/instance/__tests__/MessagePage.test.tsx
src/pages/instance/__tests__/DLQPage.test.tsx` — 65 passed. The two new
regressions fail on the parent commit (the `.ant-picker-clear` element renders)
and pass after the change.
- `cd web && npm test` — 1761 passed, 3 failures in unrelated files
(`AlertsPage`, `TopicPage`) that time out under the full parallel run; both
files pass in isolation (88/88), so they are pre-existing flakiness, not caused
by this change.
- `cd web && npm run lint` — 0 errors (10 pre-existing warnings).
- `cd web && npm run build` — passed, including the license check.
### Checklist
- [x] One coherent change; unrelated modifications are not bundled in
- [x] Commit subject follows Conventional Commits (`fix:`)
- [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 (no backend change)
- [x] New source files carry the ASF license header (no new source files)
- [x] Documentation touched where behaviour changed (no user-facing docs
needed)
--
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]
