for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
namespace Seongbae\Discuss\Notifications;
use Illuminate\Bus\Queueable;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Notifications\Messages\MailMessage;
use Illuminate\Notifications\Notification;
use Illuminate\Support\Facades\Log;
use App\Mail\TeamMemberAdded;
use Helper;
class NewThreadNotification extends Notification
{
use Queueable;
private $user;
private $thread;
private $msg;
/**
* Create a new notification instance.
*
* @return void
@return
Adding a @return annotation to a constructor is not recommended, since a constructor does not have a meaningful return value.
Please refer to the PHP core documentation on constructors.
*/
public function __construct($thread, $msg=null)
$this->thread = $thread;
$this->msg = $msg;
}
* Get the notification's delivery channels.
* @param mixed $notifiable
* @return array
public function via($notifiable)
$notifiable
This check looks from parameters that have been defined for a function or method, but which are not used in the method body.
return ['mail'];
* Get the mail representation of the notification.
* @return \Illuminate\Notifications\Messages\MailMessage
public function toMail($notifiable)
$url = route('discuss.show', ['channel'=>$this->thread->channel->slug, 'thread'=>$this->thread]);
return (new MailMessage)
->subject($this->msg)
->markdown('discuss::emails.newthread',['thread'=>$this->thread, 'url'=>$url]);
* Get the array representation of the notification.
public function toArray($notifiable)
return [
];
seongbae /
discuss
Loading history...
Adding a
@returnannotation to a constructor is not recommended, since a constructor does not have a meaningful return value.Please refer to the PHP core documentation on constructors.