pawarprasad123 opened a new pull request, #509: URL: https://github.com/apache/atlas/pull/509
## What changes were proposed in this pull request? ## Background Currently, Apache Atlas maintains three different UI implementations: Classic UI – Backbone.js New UI – Backbone.js React UI Maintaining three UI layers increases maintenance overhead, code duplication, and confusion for users and contributors. ## Objective Streamline the UI architecture by removing the legacy “New UI” built on Backbone.js, and retaining only: Classic UI (Backbone.js) React UI The goal is to reduce complexity, improve maintainability, and align with the long-term UI direction of the project. ## Scope of Work Identify and remove: New UI routes Related Backbone.js views, templates, and assets Feature toggles or flags referencing the New UI Ensure: Classic UI remains fully functional React UI remains unaffected Update: Documentation (if applicable) Navigation or routing logic pointing to the removed UI Validate: No broken links or references to the removed UI Application builds and runs successfully after cleanup ## Acceptance Criteria “New UI” (Backbone.js) is completely removed from the codebase Only Classic UI and React UI are available No references to New UI remain in routing or navigation Application works without UI-related regressions Documentation updated if required ## Notes This change is intended as a cleanup and consolidation effort No functional changes are expected in Classic or React UI ## How was this patch tested? Manually tested , build passed <img width="1834" height="1135" alt="Screenshot from 2026-01-29 14-30-31" src="https://github.com/user-attachments/assets/8f941f1d-b4d2-4844-b644-7111297006cf"; /> <img width="1850" height="1135" alt="image" src="https://github.com/user-attachments/assets/65f98c72-8956-4dcd-aecc-0060846b9c1d"; /> <img width="1850" height="1135" alt="image" src="https://github.com/user-attachments/assets/144f662d-f8ee-427c-af07-385eeea1a501"; /> -- 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]
