Connected to frontend with e2e testing on create member and sign up form

[Allimonae]

Summary

• Renames matchingPref to matchPref across the frontend
• Connect the sign-up form to the/api/members endpoint
• Add controller and service tests for member creation.

What changed?

• Renamed matchingPref to matchPref in the MemberProfileValues interface, Zod schema, and all related form field bindings and handlers in SignUpForm.tsx.
• Renamed the local matchingPrefOptions variable to matchingPreferenceOptions for clarity.
• Replaced the placeholder Promise.resolve() stub in SignUpForm's submit handler with a real POST /api/members fetch call. On success, the form is reset; on failure, an error message from the API response (or a fallback) is displayed; on network error, a connection-specific message is shown.
• Added MemberControllerTest covering successful member creation, validation rejection on blank fullName, and conflict response on duplicate email.
• Added MemberServiceTest covering successful member creation with all fields and duplicate email detection (verifying createMember on the repo is never called in that case).

How to test?

1. Run the sign-up form in the browser and submit a valid registration — confirm the form submits to /api/members, resets on success, and displays appropriate error messages on failure or network issues.
2. Submit the form with a duplicate email and confirm a conflict error is shown.
3. Run MemberControllerTest and MemberServiceTest and confirm all tests pass.

Why make this change?

The matchingPref field name was inconsistent with the backend's matchPref naming convention, causing a mismatch between the frontend payload and the API contract. The form also lacked a real API integration, relying on a placeholder stub that never actually persisted data. Tests were added to establish baseline coverage for the member creation flow.

[Allimonae]

• Connected to frontend with e2e testing on create member and sign up form #60 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

Graphite Automations

"Request reviewers once CI passes" took an action on this PR • (07/24/26)

2 reviewers were added to this PR based on Henry Chen's automation.

[Allimonae]

Merge activity

• Aug 3, 5:04 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Aug 3, 5:04 PM UTC: Graphite rebased this pull request as part of a merge.
• Aug 3, 5:05 PM UTC: @Allimonae merged this pull request with Graphite.

[sonarqubecloud]

Quality Gate passed

Issues
5 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud