Ministry Name Changes- Create a Centralized Constant
- Dominant language
- TypeScript
- Stars
- 29
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
**Acceptance Criteria**
Create a **centralized constant** so that if a name change is required ( EG- AEST to PSFS) then it doesn't have to be changed all over the place just at the source
**Question**
a lot of our environments behind the scenes have AEST... is it important to change these route names for IMB?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by searching the repository for AEST and the existing ministry-name references to identify where the value is duplicated. Confirm whether route names used by IMB should change, then centralize the approved name and update its consumers; done means the name has one source of truth and the route-name decision is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100