76-backend-logic-for-singlekitasignup-and-servicesignup

Take a quick look.

Test data:

http://localhost:3000/signup/service
{
      "consentId": "test",
      "email": "darjusch.schrand@code.berlin",
      "fullAddress": "123 Main St, City",
      "desiredStartingMonth": "September",
      "actualOrExpectedBirthMonth": "June",
      "createdAt": "2023-05-18T00:00:00Z",
      "consentedAt": "2023-05-18T00:00:00Z",
      "revokedAt": null
    }
http://localhost:3000/signup/single
{
  "email": "darjusch.schrand@code.berlin",
  "consentId": "abcdefg123456",
  "kitaId": "kitaid",
  "kitaName": "Kita A",
  "kitaDesiredAvailability": "May",
  "createdAt": "2023-05-18T00:00:00Z",
  "consentedAt": "2023-05-18T00:00:00Z",
  "revokedAt": null
}

If you want to test local you need the dev db string just request on signal. If this is merged the flow for singleKitaSignup and serviceSignup is completed.

KitaPlatzZentrale / kpz

76-backend-logic-for-singlekitasignup-and-servicesignup #77