for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
namespace Spatie\Flash;
use Illuminate\Support\Traits\Macroable;
use Illuminate\Contracts\Session\Session;
/** @mixin \Spatie\Flash\Message */
class Flash
{
use Macroable;
/** @var \Illuminate\Contracts\Session\Session */
protected $session;
public function __construct(Session $session)
$this->session = $session;
}
public function __get(string $name)
return $this->getMessage()->$name ?? null;
public function getMessage(): ?Message
$flashedMessageProperties = $this->session->get('laravel_flash_message');
if (! $flashedMessageProperties) {
return null;
return new Message($flashedMessageProperties['message'], $flashedMessageProperties['class']);
public function flash(Message $message): void
if ($message->class && static::hasMacro($message->class)) {
$methodName = $message->class;
$this->$methodName($message->message);
return;
$this->flashMessage($message->toArray());
$message->toArray()
array
object<Spatie\Flash\Message>
It seems like the type of the argument is not accepted by the function/method which you are calling.
In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.
We suggest to add an explicit type cast like in the following example:
function acceptsInteger($int) { } $x = '123'; // string "123" // Instead of acceptsInteger($x); // we recommend to use acceptsInteger((integer) $x);
public function flashMessage(Message $message): void
$this->session->flash('laravel_flash_message', $message->toArray());
public static function levels(array $methodClasses): void
foreach ($methodClasses as $method => $classes) {
self::macro($method, function (string $message) use ($classes) {
return $this->flashMessage(new Message($message, $classes));
});
spatie /
laravel-flash
It seems like the type of the argument is not accepted by the function/method which you are calling.
In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.
We suggest to add an explicit type cast like in the following example: