Investigate dependencies - visualisations.coffee#450
Investigate dependencies - visualisations.coffee#450WaelAlahamdi wants to merge 1 commit intothoth-tech:10.0.xfrom
Conversation
|
I have tested the OnTrack development environment locally with |
millyamolo
left a comment
There was a problem hiding this comment.
I tested this PR locally on the migration branch and verified the visualisation refactor behavior in-app. On the dashboard, both Progress Burndown and Task Statuses charts rendered correctly, and I did not observe regressions in chart display/interaction. The Angular service extraction plus CoffeeScript compatibility wrapper appears to preserve existing behavior while supporting the Angular migration path. I am glad to approve it.
Thirus224849242
left a comment
There was a problem hiding this comment.
Locally tested on the quality/migrate-visualisation-service branch. Entering the Task Statuses chart as a student and no console errors occurred. Looked at the diff - the new TypeScript service is well-organized with @Injectable, the CoffeeScript file is a simple wrapper with no repeated logic, and the downgradeInjectable wiring of doubtfire-angularjs.module.ts appears to be accurate. Change is localized and there are no unrelated files changed. Approving.
|
@BrianDangDev we have two approvers. @WaelAlahamdi please open an upstream pull request (against doubtfire-web) |
Description
This pull request moves the shared visualisation logic from the AngularJS CoffeeScript factory into a new TypeScript service.
The change introduces a new
visualisation.service.tsfile to hold the shared chart creation defaults, config setup, analytics tracking, and refresh logic. The service is exposed to the hybrid Angular/AngularJS application throughdowngradeInjectable, andvisualisations.coffeehas been updated to act as a compatibility wrapper so existing CoffeeScript visualisation consumers can continue to work without further changes.This change supports the ongoing migration of the project toward Angular 17 and TypeScript while preserving the current behaviour of the visualisation components.
Type of change
How Has This Been Tested?
The change was tested manually in the local development environment.
Manual testing performed
Progress Burndownchart still renders correctlyTask Statuseschart still renders correctlyAdditional checks
npx tsc -p tsconfig.json --noEmitsuccessfullyTesting Checklist:
Checklist: