Skip to content

fix: validate email format for partners and members#136

Open
mug1sha wants to merge 12 commits into
Open-Source-Kigali:devfrom
mug1sha:fix/partner-email-validation
Open

fix: validate email format for partners and members#136
mug1sha wants to merge 12 commits into
Open-Source-Kigali:devfrom
mug1sha:fix/partner-email-validation

Conversation

@mug1sha
Copy link
Copy Markdown
Contributor

@mug1sha mug1sha commented May 19, 2026

What does this PR do?

This PR adds email format validation to the addPartner and addMember endpoints using a standard regex. It prevents invalid email strings (e.g., "hello") from being persisted to the
database and includes documentation in the README regarding this validation strategy.

Related issue

Closes # (Insert issue number here)

How did you test it?

  • Run npm run typecheck to verify the controller changes.
  • Run npm test to ensure existing member functionality remains intact.
  • Manually verified the regex pattern against standard test cases (valid/invalid emails).

Checklist

  • My code builds (npm run build)
  • I added or updated tests and npm test passes
  • I updated docs/openapi.yaml if I changed any routes
  • I added a Prisma migration if I changed schema.prisma
  • I updated docs or .env.example if needed

@mug1sha mug1sha force-pushed the fix/partner-email-validation branch 2 times, most recently from b2bdecd to 1f20976 Compare May 19, 2026 15:05
@mug1sha mug1sha force-pushed the fix/partner-email-validation branch from 6530d7c to 9c1e5b2 Compare May 19, 2026 15:15
@rodriguecyber rodriguecyber requested a review from Nick-Lemy May 20, 2026 17:51
@mug1sha
Copy link
Copy Markdown
Contributor Author

mug1sha commented May 20, 2026

validate email format for partners and members fixed @Nick-Lemy @rodriguecyber

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant