123123213weqw opened a new issue, #1328:
URL: https://github.com/apache/rocketmq-dashboard/issues/1328

   ## Problem
   
   RocketMQ messages do not require tags or keys. `RocketMQMessageProvider` 
copies `MessageExt#getTags()` and `MessageExt#getKeys()` directly into the 
message response, so either field can be `null`.
   
   The web API contract currently declares both fields as required strings, and 
the Message table sorters call `localeCompare` directly. Sorting the Tag or Key 
column can therefore throw for a valid tagless or keyless message.
   
   ## Expected behavior
   
   - Model message tags and keys as nullable API data.
   - Render the existing empty-value fallback for missing values.
   - Sort Tag and Key columns without throwing.
   - Add focused page regression coverage.
   
   ## Scope
   
   Track 1 / message query UI reliability.
   


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