#523 - Replace DataManager dynamic usage with explicit dependencies
@brijesh-amin is already working on this.
Since Jul 17, 2026.
Assessment
This issue has not been assessed yet.
Description
Parent: #523
Objective
Reduce hidden coupling and improve testability by moving from dynamic DataManager usage to explicit dependencies in targeted paths.
In scope
- Identify one or two high-traffic controllers/services using
new DataManager(...) - Replace with explicit repository/db dependency injection (module-level singleton or constructor-injected, based on repo conventions)
- Remove unused constructor argument patterns and tighten types where touched
Acceptance criteria
- No new
new DataManager(config)call sites introduced - Selected paths use explicit dependencies instead of dynamic proxy behavior
- Tests updated to mock explicit boundaries
- Behavior remains backward-compatible
Notes
Coordinate with the plan vertical-slice issue to avoid duplicate refactors.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bcgov/range-api
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
melgarafael/DeskcommCRM#1451 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·