refactor(resources): retire the AngularJS Dashboard shell (#6589) - #6620
Merged
Conversation
…s to resources-application (#6589) The twelve platform-wide extension points application-{perspectives, views, menus, settings, locales, shells, themes, tile, windows, subviews, reports} and dashboard-widgets were declared by the AngularJS Dashboard shell, but their consumers sit far outside it - the Harmonia shells, the Harmonia UI template's perspective extension, Inbox, Documents, platform-core, the settings and translation views. They move next to application-projections in resources-application, which is the shell that actually aggregates them, so the AngularJS module can be removed in the following commit. Lookup is by extension-point NAME (ExtensionsFacade.getExtensions), so nothing about resolution changes; only the declaring location does. Part of #6591. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
resources-dashboard hosted the AngularJS-generated application perspectives at /services/web/dashboard/. Those templates were removed in #6588, so the shell has no consumer left: the generated apps are Harmonia SPAs served per project, and the Harmonia application shell in resources-application is the launchpad. Removed with it: the Dashboard and Reports AngularJS perspectives, the shared EntityService/ProcessTasks AngularJS services (their only consumers were the generated AngularJS views), the module's i18n and images, and the three Maven wirings. The extension-point declarations moved to resources-application in the preceding commit. The Harmonia application shell keeps its id (applicationShell), its label (Applications) and its /services/web/application/ URL - renaming it was considered and dropped. Migration: already-generated AngularJS applications stop working at runtime, since their views load shell assets from /services/web/dashboard/. Regenerating with the Harmonia template is required, not optional. Part of #6591. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
delchev
force-pushed
the
refactor/retire-dashboard-shell
branch
from
August 8, 2026 06:16
5d1dac7 to
0364a4a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #6589. Part of the umbrella #6591.
resources-dashboardhosted the AngularJS-generated application perspectives at/services/web/dashboard/. Those templates went in #6588, so it has no consumer left — generated appsare Harmonia SPAs served per project, and
resources-applicationis the launchpad.Two commits, in this order (the first is a hard prerequisite):
points —
application-{perspectives,views,menus,settings,locales,shells,themes,tile,windows,subviews,reports}and
dashboard-widgets— whose consumers sit far outside the AngularJS stack (the Harmonia shells,the Harmonia UI template's
perspective.extension, Inbox, Documents, platform-core, the settings andtranslation views). They move next to
application-projectionsinresources-application, the shellthat actually aggregates them. Lookup is by extension-point name, so resolution is unchanged.
EntityService/ProcessTasksservices, i18n, images — plus the three Maven wirings. Two docs referencing the deletedprocess-tasks.jsnow point at the Harmonia runtime'sprocessTasksstore.Out of scope, deliberately: no rename of the Harmonia application shell. It keeps id
applicationShell, labelApplicationsand/services/web/application/.Migration note
Already-generated AngularJS applications stop working at runtime — their views load shell assets from
/services/web/dashboard/. Regenerating with the Harmonia template is required, not optional.Verification (running instance)
/services/web/dashboard/{index.html,perspectives/dashboard.html,services/process-tasks.js}→ 404/application/extension-points/…, none from/dashboard/web/dashboard|resources-dashboard|dashboard/services/process-tasksover components,tests and build is empty (one historical comment in an IT left alone)
mvn -T 1C clean package -P quick-buildgreen🤖 Generated with Claude Code