Aias00 opened a new issue, #858: URL: https://github.com/apache/rocketmq-dashboard/issues/858
### What happened RocketMQ Studio topic write APIs accept JSON literal `null` request bodies: - `POST /api/topics/create` - `POST /api/topics/update` - `POST /api/topics/delete` - `POST /api/topics/send` The controller passes these request objects directly into `MetadataService` or dereferences them before the service call. A null body can therefore be forwarded into the admin layer or fail with an internal `NullPointerException` instead of a structured 400 response. ### Expected behavior Topic write APIs should reject missing or JSON `null` request bodies with a clear 400 response, and the metadata service should guard direct create/update/send calls to avoid forwarding null commands to the admin client. ### Why this matters Topic management is part of the RocketMQ Studio metadata management baseline. Invalid write requests should fail predictably and avoid surfacing internal implementation errors. ### Scope RocketMQ Studio / track 1 metadata and topic management. -- 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]
