Add backend support for icons

[kingwrg]

Pull Request Summary

Backend Changes

1. Model Changes:

   • Goal Model:
     • Added a new Icon property to store the goal's icon.

2. Controller Changes:

   • GoalController:
     • Added a new endpoint to update the Icon property of a goal.
     • Introduced UpdateIconRequest class to handle the icon update request.

3. Service Changes:

   • GoalsService:
     • Updated the UpdateAsync method to support partial updates using UpdateDefinition.
   • IGoalsService Interface:
     • Modified the UpdateAsync method signature to accept UpdateDefinition<Goal>.

4. Configuration Changes:

   • Updated the MongoDB connection string in the configuration file.

5. Testing Changes:

   • FakeGoalsService:
     • Implemented a simulated UpdateAsync method.
   • GoalControllerTests:
     • Changed test methods' return type to async Task for proper async handling.

Summary

• Extended the backend to support new API endpoints for updating goal icons.
• Integrated the frontend with the new backend endpoints.
• Added tests to verify the backend and frontend integration, ensuring proper async handling in test methods.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	MongoDB Credentials	1e4fd13	CommBank-Server/Secrets.json	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}