14 Commits

Author	SHA1	Message	Date
Moriz Wahl	88de09b1ba	test that existing emails do not throw anymore	2023-01-27 16:03:27 +01:00
Wolfgang Huß	f9de1f05da	Fix query 'VerifyNonce' from node type 'UnverifiedEmailAddress' to 'EmailAddress'	2021-03-17 16:42:04 +01:00
Moriz Wahl	b2ab320270	nonce changed to 5 digit string, ValidateNonce query added	2021-03-02 04:35:53 +01:00
roschaefer	276ea79e8f	Update prettier to v2	2020-03-24 21:11:11 +01:00
roschaefer	9e2baf25d2	Don't remove dots in emails	2019-11-28 11:22:09 +01:00
roschaefer	61a8914989	Always normalize email in backend	2019-11-05 00:06:15 +01:00
roschaefer	1e31a0c620	fix: remove previous email address on change ... This will allow you to change back to your previous email address: The backend won't complain because of a user who owns that email address already.	2019-10-02 01:55:14 +02:00
roschaefer	e6f8bbac9b	fix: remove copy+paste oversights ... In the registration resolvers, it makes sense to immediately resolve if an email address has been found (because you can re-send the registration email). In this case, we use the helper method only to trigger the `UserInputError`.	2019-10-02 01:54:28 +02:00
roschaefer	6a7970200f	refactor: EmailAddr.Request -> UnverifiedEmailAddr.	2019-10-02 01:21:56 +02:00
roschaefer	5848e6af18	Fix a TODO by @alina-beck	2019-10-02 00:54:01 +02:00
roschaefer	e116d52992	Use EmailAddressRequest and validate email	2019-10-02 00:54:01 +02:00
roschaefer	e51124f316	Resolvers for EmailAddress implemented	2019-10-02 00:54:01 +02:00
roschaefer	8c13234af9	Handle edge case ... It might be that people try to register email addresses that they don't own. Then if the actual owner tries to add this email address, she should not get a unique constraint violation. Instead the email will be re-used. Is this a security issue? Because we re-use the nonce? 🤔	2019-10-02 00:54:01 +02:00
roschaefer	73d5abd724	Implement AddEmail resolver	2019-10-02 00:54:01 +02:00