Support icons

[swathimanoharan1]

Task 1 – Backend: MongoDB, Model Update, and Manual API Test
✅ Extended the Goal model in C# to include a new Icon field.

✅ Seeded the local MongoDB instance with test data.

✅ Used Postman to manually test the updated GET and POST endpoints.

✅ Verified icon data is correctly stored and retrieved in the API response.

✅ Exported a .json sample of the API response to validate backend correctness.

Task 2 – Frontend: React/Redux Integration & Icon Support
✅ Cloned and set up the rWEB repo.

✅ Updated the TypeScript Goal model to include the icon field.

✅ Integrated an emoji picker using emoji-mart package for user-friendly icon selection.

✅ Modified GoalManager.tsx component to:

Display the current icon (if any)

Allow icon selection via emoji picker

Update local state and Redux store accordingly

✅ Uploaded the updated GoalManager.tsx file as requested.

Task 3 – Networking: Backend ↔ Frontend Wiring for Icon Persistence
✅ Implemented a PUT request handler (updateGoal) in the backend API using Axios.

✅ Called this PUT request in the emoji pick event handler to persist the selected icon.

✅ Confirmed that icon changes now persist across page reloads and server restarts.

✅ Uploaded the lib.ts file containing the new PUT request implementation.

Task 4 – Testing: Unit Tests with xUnit for Icon Support
✅ Added unit test GetForUser in GoalControllerTests.cs using xUnit.

✅ Mocked IGoalsService and IUsersService using fake implementations.

✅ Asserted that:

API returns goals correctly for a given user

Each returned object is a Goal with the expected UserId

✅ All test cases pass locally.

✅ Uploaded the updated GoalControllerTests.cs for review.

[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	f46d1ce	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.}