-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature - Allow users to be deleted #1592
base: master
Are you sure you want to change the base?
Conversation
d8fb3a3
to
ebbe9b8
Compare
ebbe9b8
to
290b70d
Compare
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 haven't played with it locally but this looks flawless 🔥 💯
private | ||
|
||
def organic_domain_for(user) | ||
Mumukit::Platform.laboratory.organic_domain(user.last_organization) |
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.
Prefer to explicitly obtain organization from where the user clicked delete profile button
|
||
<div class="row"> | ||
<div class="col-md-12"> | ||
<%= t :delete_account_confirmation_email_explain_html, user_email: @user.email, support_email: Rails.configuration.reminder_sender_email %> |
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.
This is not for you to address it @faloi, but we should define another configuration for Mumuki general purpose email
🎯 Goal
Closes mumuki/mumuki-domain#86
Allow users to be deleted.
🔜 Future work
I've only included a very basic text version of the confirmation email, it should be extended and complemented with an HTML version.
📸 Screenshots
Step 1 - delete request
Step 2 - delete confirmation, coming from email
Perhaps a bit confusing, because the modal is the same as previous step... we can change the text or the button, whatever.
Step 2 - invalid or expired token
I'm treating both cases the same way for security reasons - after all the user cannot do anything but starting the delete process again.
Step 3 - user disabled
Maybe we can also force a logout here or redirect to a "goodbye" page.