Cancel signup link

[maddiedierker]

Note: change base before merging!

What it does

• Adds GET /users/cancel route to cancel an in-progress partial registration
• Adds a link to users_cancel_path in the finish signup form
• Logs the event to redshift:

study: 'account-sign-up-v2',
study_group: 'experiment-v2',
event: 'cancel-finish-sign-up',
data_string: session[:sign_up_uid]

Examples

OAuth accounts:

Email accounts (i.e., user where provider is nil):

[maddiedierker]

I feel okay about relying on having @user.email set at this point (the user shouldn't be able to get to this point if we don't have an email for their account), but would like to hear others' feedback on this.

[islemaster]

Now that we're not sending Clever through this path I suppose it's fine; we may end up with other providers that don't send over an email in the future. (Powerschool?)

That won't cause an error though, just an odd string - I'm okay if we want to cross that bridge when we come to it.

[islemaster]

I've got suggestions, but this looks great!

[islemaster]

Now that we're not sending Clever through this path I suppose it's fine; we may end up with other providers that don't send over an email in the future. (Powerschool?)

That won't cause an error though, just an odd string - I'm okay if we want to cross that bridge when we come to it.

[islemaster]

Is there a particular reason to return session here?

[maddiedierker]

for unit tests, which i feel kind of meh about. being able to create a fake session, pass it in to the method (which is necessary either way), and return it made testing this method more straightforward

[islemaster]

I know we haven't spec'd it, but it might be helpful to send a metrics event for cancel right before we end sign-up tracking here.

[maddiedierker]

good call. i'll add a cancel event that gets logged for the experiment group (which is currently the only group that sees the "cancel" link)