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

   ## Problem
   
   RocketMQ Studio still uses Ant Design component properties that are 
deprecated by the installed Ant Design version across several runtime pages:
   
   - `Card.bodyStyle`
   - `Card.bordered`
   - `Modal.destroyOnClose`
   
   Opening the affected pages produces development-console warnings and leaves 
the code dependent on APIs scheduled for removal. The warnings also obscure 
actionable runtime diagnostics during local verification.
   
   The ACL page and the Settings `InputNumber` warning are intentionally out of 
scope because open PRs #1757 and #1771 already cover those files.
   
   ## Confirmed locations
   
   The remaining usages are present in cluster, instance, operations, and 
Studio pages, including:
   
   - `web/src/pages/cluster/{certs,clients,index}.tsx`
   - `web/src/pages/instance/{consumer,dlq,index,message,topic}.tsx`
   - `web/src/pages/ops/alerts.tsx`
   - 
`web/src/pages/studio/{AlertManagement,BrokerCluster,GroupManagement,LiteTopic,Producer,Proxy,SslSettings}.tsx`
   
   ## Expected behavior
   
   - Replace `bodyStyle` with `styles.body`.
   - Replace `bordered={false}` with `variant="borderless"`.
   - Replace `destroyOnClose` with `destroyOnHidden`.
   - Preserve the current rendering, modal lifecycle, and page behavior.
   - Keep ACL and Settings changes out of this scope to avoid overlapping open 
PRs.
   
   ## Validation
   
   - The affected files no longer contain the deprecated properties.
   - Targeted page tests continue to pass.
   - The frontend production build succeeds.
   
   ## Scope
   
   Track 1: AI-Native unified management platform frontend compatibility and 
maintainability.
   


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