As there are so many different ways of setting up a web app, I think it's going to be difficult to get this option working well. I propose to remove this argument and have a simple setup which is easy to edit.
Outline for version 3.0
The new Openmaize.Login Plug will not have a unique_id option. It will accept either email or username as user-identifier and can easily be customized to accept other identifiers.
The database files will have email and username entries, and will use email to index each user.
The session/new.html.eex form will just have email and password inputs.
All the other forms will have input boxes for email, username (and password if necessary).
We could also drop all the references to username.
As there are so many different ways of setting up a web app, I think it's going to be difficult to get this option working well. I propose to remove this argument and have a simple setup which is easy to edit.
Outline for version 3.0
The new Openmaize.Login Plug will not have a
unique_id
option. It will accept eitheremail
orusername
as user-identifier and can easily be customized to accept other identifiers.The database files will have
email
andusername
entries, and will useemail
to index each user.The
session/new.html.eex
form will just haveemail
andpassword
inputs.All the other forms will have input boxes for
email
,username
(andpassword
if necessary).We could also drop all the references to
username
.