pilichoumao opened a new pull request, #6396: URL: https://github.com/apache/rocketmq-dashboard/pull/6396
### Which Issue(s) This PR Fixes Fixes #6395. ### Brief Description A context name containing LF/TAB makes `config get-contexts` print extra rows. Dynamic headers and mutation metadata bypass the existing escaping, and VT/FF/ESC in row values still alter the display. Escape ASCII C0/DEL at every table-cell boundary, preserving the existing TAB/LF/CR spellings and using visible hex escapes for the other controls. Keep ordinary UTF-8, literal backslashes, stored config and JSON/YAML content. This completes the boundary introduced by #4661; #5624 addresses display width separately. No new dependencies or changes to authentication/confirmation. ### How Did You Test This Change? Baseline: `rocketmq-studio@779b8c0e7aed2396d3cc72743dcd544ea48e9ae6`. macOS, Go 1.27.1; serial execution with `GOMAXPROCS=1 GOMEMLIMIT=384MiB GOFLAGS=-p=1`. - Same added regressions on unchanged production: the control-character cases fail; Unicode and JSON/YAML compatibility controls pass. With this fix all six regression functions pass, including a real stored-config App command and real HTTP Result envelopes rendered through the App. - `go test -race -parallel 1 -count=1 -timeout=60s ./...`: all packages pass. - `make fmt`, `make vet` (includes `catalog-verify`), `make build-all`: pass; all six targets and their generated/verified license materials pass. - Temporary composition with #5624's production/go.mod patch: the new cases fail with that patch alone; current output and cmd race suites pass after applying the cell escaping at its renderer boundary. Those width changes are not included here. - `git diff --check`: pass. README documents the display/structured-output distinction. ### Checklist - [x] One coherent change - [x] Conventional Commit - [x] Regression tests named `...Test`; ASF headers present - [x] Behavior documented - [x] No new UI text or Java architecture changes -- 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]
