Frun1na opened a new issue, #4742:
URL: https://github.com/apache/rocketmq-dashboard/issues/4742

   ### Before Creating the Bug Report
   
   - [x] I have searched the [open 
issues](https://github.com/apache/rocketmq-dashboard/issues) and found no 
similar issue.
   
   ### What Happened
   
   On the Consumer Group page, the protocol tags in a group's client list (实例 / 
clients column) render
   with the default gray color instead of the intended green (gRPC) / geekblue 
(Remoting).
   
   `PROTOCOL_MAP` in `web/src/constants/theme.ts` is keyed by `REMOTING` / 
`GRPC`, but the server
   serializes the `Protocol` enum by its enum name — `gRPC` / `Remoting`
   (`org.apache.rocketmq.studio.common.domain.enums.Protocol`). The lookup 
therefore never matches, and
   the render falls back to `{ labelKey: protocol, color: 'default' }`: the 
text is still correct
   (because `t(protocol)` echoes the raw value), but the color is lost.
   
   The map only ever matched the stale mock data in 
`web/src/mock/consumers.ts`, which used the same
   uppercase shells; `mock/clients.ts` already uses the real values, which is 
why the clients page
   renders its protocol tags correctly.
   
   ### Expected Behavior
   
   Protocol tags on the consumer page carry the same colors as on the clients 
page: green for `gRPC`,
   geekblue for `Remoting`.
   
   ### Steps to Reproduce
   
   1. Open an instance's Consumer Group page and expand a group's client 
instances (or open the group
      detail modal).
   2. Look at the 协议 column: the tag text is correct (`gRPC` / `Remoting`) but 
the color is the
      default gray, unlike the clients page.
   
   ### Environment
   
   - RocketMQ Studio `rocketmq-studio` @ `7ce9a682`
   - Frontend: `web/src/constants/theme.ts` (`PROTOCOL_MAP`), 
`web/src/pages/instance/consumer.tsx`
   
   ### Are You Willing to Submit a Pull Request?
   
   Yes — #4741 fixes this.
   


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