Update campaignUtils.ts for update target fix

[ashish-egov]

Summary by CodeRabbit

• Refactor
  • Improved internal logic for managing project targets
  • Added a helper function to streamline target updates and additions
  • Enhanced code maintainability and type safety

[coderabbitai]

Walkthrough

The pull request introduces a new helper function updateOrAddTarget in the campaign utilities module. This function is designed to manage project targets more efficiently by providing a centralized method for updating or adding targets based on beneficiary types. The change refactors the existing target management logic to improve code clarity and maintainability, explicitly defining the targets array type and encapsulating the target update process in a dedicated function.

Changes

File	Change Summary
health-services/.../campaignUtils.ts	Added updateOrAddTarget helper function to manage project targets with improved logic for updating or adding targets

Poem

🐰 In the realm of code, a rabbit's delight,
A function springs forth, making targets just right
updateOrAddTarget, clean and precise
Refactoring logic with algorithmic spice
Targets now dance with elegance bright! 🎯

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[ashish-egov]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[ashish-egov]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f13f4cf and 64e8d07.

📒 Files selected for processing (1)

• health-services/project-factory/src/server/utils/campaignUtils.ts (1 hunks)

🧰 Additional context used

🪛 Biome (1.9.4)

health-services/project-factory/src/server/utils/campaignUtils.ts

[error] 2364-2364: This let declares a variable that is only assigned once.

'targets' is never reassigned.

Safe fix: Use const instead.

(lint/style/useConst)

---

[error] 2369-2369: Use Number.parseInt instead of the equivalent global.

ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.

(lint/style/useNumberNamespace)

🔇 Additional comments (1)

health-services/project-factory/src/server/utils/campaignUtils.ts (1)

2383-2394: Validate edge cases for the target updating logic.
If the existing target is updated or a new one is added, ensure your tests cover both scenarios (e.g., repeated updates, zero or negative target values) to confirm the function’s correctness under all conditions.