-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add SentEmailMixin::assertLastEmailSentTo()
(and rename assertEmailSentTo()
to assertFirstEmailSentTo()
#17
Comments
Hey @myselfhimself! Interesting. This method is sort of intended as a quick and dirty solution. We can't change it's behaviour now as it would be a BC break. You could use the underlying code yourself in the test and change Alternatively, I'd be ok adding a |
Hello Kevin,
I let you decide :)
Le jeu. 27 oct. 2022 à 16:57, Kevin Bond ***@***.***> a
écrit :
… Hey @myselfhimself <https://github.com/myselfhimself>!
Interesting. This method is sort of intended as a quick and dirty
solution. We can't change it's behaviour now as it would be a BC break. You
could use the underlying code yourself in the test and change first() to
last().
Alternatively, I'd be ok adding a SentEmailMixin::assertLastEmailSentTo()
method. If we do, for consistency we should add
SentEmailMixin::assertFirstEmailSentTo() and deprecate
SentEmailMixin::assertEmailSentTo().
—
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJU5QUNQPLREZFZPT22JYLWFKJ6JANCNFSM6AAAAAARQB3MM4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ok, I'll leave this issue open as a feature request.
Were you able to do this to get your test passing? |
SentEmailMixin::assertLastEmailSentTo()
(and rename assertEmailSentTo()
to assertFirstEmailSentTo()
I used:
and got my test passing. Thank you |
Hello!
currently
SentEmailMixin::assertEmailSentTo
does:checking the first() email that was sent to someone...
Though in general testing (or in my case)... I am interested in the most recent email.. so the last()..
This is not a bug... But by design, do we want
last()
instead offirst()
for that method?Thank you :)
The text was updated successfully, but these errors were encountered: