Refactor: migrate units index state from AngularJS to Angular

[JeffySam]

Summary

This PR performs a strict migration of the Units Index state from AngularJS (CoffeeScript) to Angular.

The legacy AngularJS state and template have been fully removed and replaced with an Angular component and Angular-managed UI-Router state.

Changes

• Removed legacy CoffeeScript state and template:

  • index.coffee
  • index.tpl.html

• Added Angular replacements:

  • index.component.ts
  • index.component.html
  • index.component.scss
  • index.state.ts
  • Updated projects/states/index/index.coffee to remove dependency on deleted units/states/index/index.tpl.html (compatibility fix).
  • src/app/projects/states/index/index.coffee was updated only to remove templateUrl: "units/states/index/index.tpl.html" because that template is deleted as part of strict migration.

• No CoffeeScript remains for units/index state.

• Registered the new Angular state in doubtfire.states.ts

• Updated dependent AngularJS state to delegate rendering to Angular

• Added a minimal AngularJS shim module (index.ajs.module.ts) to preserve module dependency resolution (no logic, no state)

Migration Notes

• This is a strict migration (no hybrid controller or template usage)
• AngularJS is no longer responsible for routing or rendering this feature
• The shim module exists solely to prevent AngularJS module resolution errors
• Application boots successfully, login works, and unit pages load correctly

Testing

• npm start
• Verified login flow
• Navigated to unit pages (/units/:unitId)
• Confirmed Angular component renders and routing functions as expected

[SteveDala]

Hi Jeffy, is this Pull Request meant to be against the 9.x branch rather than the development branch?

[sabdosh]

Hey Jeffy, I have had a look at your PR locally on my machine and ran the test as described. Login works, but navigating to a unit page triggers a runtime error in the console:

TypeError: Cannot read properties of undefined (reading 'activeTasks') originating from AngularJS (StateTaskResult.fromUiParams).

This indicates AngularJS state/controller code is still executing and the data contract with the new Angular Units Index component is currently broken.
Although the new Angular files are present, the migration is not clean at runtime and contradicts the PR’s testing claims that unit pages “load correctly”.
Recommend addressing this integration issue before merge.

[mannat2634]

Hi Jeffy, I'm also facing similar error and I don't even see tasks being displayed.

Looks like the issue is that you changed projects/index to use an empty <ui-view></ui-view> template, but the ProjectsIndexStateCtrl controller still needs to run and populate $scope.project for the child states. The dashboard state depends on $scope.project being there.

Probably need to either migrate the ProjectsIndexStateCtrl to an Angular component or make sure it still initializes properly with the new setup. Could also create a shared template that both units and projects can use instead of removing the old one entirely.

Try navigating to any project's dashboard to see it break.

[rubalpreet-singh-123]

Hi Jeffy, I pulled this PR locally and ran it on my machine following the testing steps mentioned. The application starts correctly and the login flow works as expected. However, when navigating to a unit page, I’m consistently seeing a runtime error in the browser console.

The error appears to originate from AngularJS, specifically related to attempting to read activeTasks from an undefined object (StateTaskResult.fromUiParams). This suggests that some AngularJS state or controller logic is still executing at runtime, and the data contract expected by the new Angular Units Index component is not being satisfied.

Although the new Angular files are present, this indicates that the migration is not fully clean at runtime and contradicts the claim that unit pages are loading correctly. I would recommend resolving this integration issue before merging.

I’m also observing a similar issue where tasks are not displayed at all. It looks like projects/index has been updated to use an empty , but ProjectsIndexStateCtrl still needs to execute to initialise $scope.project for child states. This causes downstream dashboard views to break.

It may be necessary to either migrate ProjectsIndexStateCtrl into an Angular component or ensure it still initialises correctly under the new setup. Another option could be introducing a shared template that both units and projects can rely on, instead of removing the legacy implementation entirely. You can reproduce the issue by navigating to any project dashboard.