-
Notifications
You must be signed in to change notification settings - Fork 308
Conversation
9be01a3
to
8ba8127
Compare
8ba8127
to
7a59215
Compare
b435633
to
f82f314
Compare
062cc52
to
b2d6fe1
Compare
26bad64
to
06056fa
Compare
b2d6fe1
to
b317926
Compare
06056fa
to
bd7d0c1
Compare
b317926
to
d4a22db
Compare
bd7d0c1
to
11ebe8a
Compare
d4a22db
to
6713c9a
Compare
11ebe8a
to
171cf54
Compare
28d9225
to
c0d2aca
Compare
Re: feature flags: https://martinfowler.com/articles/feature-toggles.html Many caveats and best practices in there, e.g.:
|
In the interest of standardizing URLs. Current count is 60 - vs. 6 _.
I see so many similarities between email and accounts elsewhere. We talked about this before (should dig up): why don't we expand the accounts elsewhere machinery to encompass emails? |
def with_email_and_username(cls, email, username): | ||
"""Return a new participant with given email and username | ||
""" | ||
username = username and username.strip() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not just username = username.strip()
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And why not push that down into _validate
?
@@ -81,6 +81,28 @@ def with_random_username(cls): | |||
return cls.from_username(username) | |||
|
|||
@classmethod | |||
def with_email_and_username(cls, email, username): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer to see this use the existing username.safely_reserve
infrastructure for consistency and code reduction.
@@ -46,7 +46,7 @@ | |||
text-align: center; | |||
display: none; | |||
background: transparentize($light-brown, 0.3); | |||
z-index: 1000; | |||
z-index: 900; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume this is for a reason, ya?
Running into issues on my Macbook, but still running fine on the Ubuntu VM. |
3d2430c
to
b80f821
Compare
Rebased, was 114f36c. |
b80f821
to
4bc67bc
Compare
89a3ed3
to
13a8cc9
Compare
Coming back here from #4604 ... I am thinking about taking the stub participant approach discussed at ... somewhere? We already have plumbing for routes and exchanges and email addresses, seems wrong to duplicate those to enable anon to make payments. Better to stub out a participant, send a normal email verification, and then populate the return page with a "Confirm Payment" section similar to how we could do package claims on the receiver side. |
|
send_link → send-link
Closing as stale |
#1052.
This PR allows users to sign-in or create an account on Gratipay using email.
Screenshots
Email HTML
Email text
Signup flow (GIF)
(http://recordit.co/ZJwXHLYiHF)
Signin flow (GIF)
(http://recordit.co/SX6hYCQI7j)
Non-critical items to reticket
email_auth_nonces
Todo
-
instead of_
in URLs—Add email auth #4539 (comment): send_link → send-link #4550auth/verify
Participant.with_*
—Add email auth #4539 (comment)