Skip to content
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

Send welcome email when user created by login with proton #1115

Conversation

cquintana92
Copy link
Collaborator

No description provided.

@@ -8,6 +8,7 @@ def test_available_sl_domains(flask_client):
user = create_new_user()

assert set(user.available_sl_domains()) == {"d1.test", "d2.test", "sl.local"}
assert user.created_by_partner is False
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's better to create a dedicated test for this field, this test is rather about SL domains.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved it into a different test

@@ -182,6 +182,9 @@ def process(self) -> LinkResult:
)
Session.commit()

if not new_user.created_by_partner:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you know in what case new_user.created_by_partner can be True here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When called from the partner_api this flag will be True

@nguyenkims nguyenkims merged commit dd0598a into master Jun 28, 2022
@nguyenkims nguyenkims deleted the feature/send-welcome-email-when-user-created-by-login-with-proton branch June 28, 2022 09:57
@acasajus acasajus added the fix label Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants