From f289680d980a2c262df1e1fe5a3e39137cbcd958 Mon Sep 17 00:00:00 2001
From: Harvey Tindall <hrfee@protonmail.ch>
Date: Sun, 4 Aug 2024 13:57:42 +0100
Subject: [PATCH] users: remove notes

---
 users.go | 26 +-------------------------
 1 file changed, 1 insertion(+), 25 deletions(-)

diff --git a/users.go b/users.go
index e5525cb..106a854 100644
--- a/users.go
+++ b/users.go
@@ -48,31 +48,7 @@ type NewUserData struct {
 	Log     func()
 }
 
-// FIXME: First load of steps are going in NewUserFromInvite, because they're only used there.
-// Make an interface{} for Require/Verify/ExistingUser which all contact daemons respect, then loop through!
-/*
--- STEPS --
-- Validate Invite
-- Validate CAPTCHA
-- Validate Password
-- a) Discord  (Require, Verify, ExistingUser, ApplyRole)
-  b) Telegram (Require, Verify, ExistingUser)
-  c) Matrix   (Require, Verify, ExistingUser)
-  d) Email    (Require, Verify, ExistingUser)
-* Check for existing user
-* Generate JF user
-- Delete Invite
-* Store Activity
-* Store Email
-- Store Discord/Telegram/Matrix/Label
-- Notify Admin (Doesn't really matter when this happens)
-* Apply Profile
-* Generate JS, Ombi Users, apply profiles
-* Send Welcome Email
-
-
-*/
-
+// Called after a new-user-creating route has done pre-steps (veryfing contact methods for example).
 func (app *appContext) NewUserPostVerification(p NewUserParams) (out NewUserData) {
 	// Some helper functions which will behave as our app.info/error/debug
 	deferLogInfo := func(s string, args ...any) {