Name audit strings
Description
audit uses repeated inline string literals (keys, codes). This issue centralizes them.
Requirements and context
- Repository scope: Talenttrust/Talenttrust-Backend only.
- Move the audit literal strings into a constants module and reference them.
- Behaviour identical; no string value changes.
- Tests pass.
Suggested execution
- Fork the repo and create a branch
git checkout -b refactor/audit-61-strconsts
- Implement changes
- Write code in: the relevant module.
- Write comprehensive tests in: cover the new behaviour and edge cases.
- Test and commit
Test and commit
- Run
npm run lint, npm test, and npm run build.
- Cover edge cases: values unchanged, tests pass.
- Include the full test output in the PR description.
Example commit message
refactor(audit): extract string constants
Guidelines
- Minimum 95 percent test coverage for impacted modules.
- Clear, reviewer-focused documentation.
- Timeframe: 96 hours.
Community & contribution rewards
- 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
- ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated.
Name audit strings
Description
audit uses repeated inline string literals (keys, codes). This issue centralizes them.
Requirements and context
Suggested execution
git checkout -b refactor/audit-61-strconstsTest and commit
npm run lint,npm test, andnpm run build.Example commit message
refactor(audit): extract string constantsGuidelines
Community & contribution rewards