roschaefer f3c31aed28 Don't expose termsAndConditionsAgreedAt ...

1. Don't expose `termsAndConditionsAgreedAt` as input param, because of ..why?
2. Make the `termsAndConditionsAgreedVersion` a *required* input param
   for `SignupVerification`. If new users register, they have to confirm
   the terms and conditions. I added another test to check what happens if
   the user sends `null`.
3. Sorry @ogerly for confusing you with my review here:
   https://github.com/Human-Connection/Human-Connection/pull/1556#pullrequestreview-287516516
   What I meant is that we want to simulate a user with no
   `termsAndConditionsAgreedVersion`. But of course the `variables` must
   have it set when you run the mutations. Now we have the
   exclamation mark in the input param, see point 1 ☝️

2019-09-13 01:11:46 +02:00

..

resolvers

Don't expose termsAndConditionsAgreedAt

2019-09-13 01:11:46 +02:00

types

Don't expose termsAndConditionsAgreedAt

2019-09-13 01:11:46 +02:00

helpers.js

Coerce undefinedToNull in embed resolver

2019-07-22 00:38:56 +02:00

index.js

Remove a lot of unused code, reduce graphql schema

2019-09-05 03:20:32 +02:00