-
Notifications
You must be signed in to change notification settings - Fork 11.7k
[6.x] Changed Contract to Class #30088
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
Conversation
|
Think we should thread a little careful here. This cascades a little higher up the chain to the queue method I see. |
- I have changed `\Illuminate\Contracts\Mail\Mailable` to `\Illuminate\Mail\Mailable`, since contract does not contains `cc` / `to` / `bcc` / `locale` methods, and in case if you call method only with contract, then we will get fatall error, since method is not present in the contract
4119603 to
de16868
Compare
|
FIxed in all places, where this method is called. |
|
I really think we shouldn't do this on a minor release. Seems to be breaking? |
|
hm, |
- expand Mailable interface since `PendingMail::fill()` used some not existed method from the Mailable interface now. And it will caused an fatal error. Base PR: laravel#30088
|
#30089 changed to 7.0 |
- expand Mailable interface since `PendingMail::fill()` used some not existed method from the Mailable interface now. And it will caused an fatal error. Base PR: #30088
- expand Mailable interface since `PendingMail::fill()` used some not existed method from the Mailable interface now. And it will caused an fatal error. Base PR: laravel/framework#30088
- expand Mailable interface since `PendingMail::fill()` used some not existed method from the Mailable interface now. And it will caused an fatal error. Base PR: laravel/framework#30088
\Illuminate\Contracts\Mail\Mailableto\Illuminate\Mail\Mailable, since contract does not containscc/to/bcc/localemethods, and in case if you call method only with contract, then we will get fatall error, since method is not present in the contract