You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 24, 2018. It is now read-only.
A sponsor should only be able to "sign up" providing they have a authorised email address and sign up, one-time code - with which they can then make a password.
My current thinking is extend the auth package to have an interface for any type of auth auth/email-password/CSG login. Also by creating a base Auth struct and have other types that implement the interface based off of the Auth struct (using go's struct composition). Very much open to thoughts on this.
The text was updated successfully, but these errors were encountered:
A sponsor should only be able to "sign up" providing they have a authorised email address and sign up, one-time code - with which they can then make a password.
My current thinking is extend the auth package to have an interface for any type of auth auth/email-password/CSG login. Also by creating a base
Auth
struct and have other types that implement the interface based off of theAuth
struct (using go's struct composition). Very much open to thoughts on this.The text was updated successfully, but these errors were encountered: