IMHO, the current Database channel for saving notifications in Laravel is really bad design:
I solved a similar problem by customizing notification class:
create the class for this action:
artisan make:notification NewQuestion
inside it:
public function __construct($user,$question)
{
$this->user=$user;
$this->question=$question;
}
...
public function toDatabase($notifiable){
$data=[
'question'=>$this->(array)$this->question->getAttributes(),
'user'=>$this->(array)$this->user->getAttributes()
];
return $data;
}
then you can access proper data in view or controller like this:
@if($notification->type=='App\Notifications\UserRegistered')
New question from {{$notification->data['user']['name']}}
@endif