New command - make:message for Messenger

[weaverryan]

An easy one - generated for Messenger - generates an empty message class and corresponding handler:

Generated Code

SendWelcomeEmailMessage

<?php

namespace App\Message;

class SendWelcomeEmailMessage
{
    /*
     * Add whatever properties & methods you need to hold the
     * data for this message class.
     *
     * Note - if you're handling this message async, you may need
     * a getter & setter method for each property so that it serializes
     * and unserializes correctly.
     */

//     private $name;
//
//     public function __construct(string $name)
//     {
//         $this->name = $name;
//     }
//
//    public function getName(): string
//    {
//        return $this->name;
//    }
//
//    public function setName(string $name)
//    {
//        $this->name = $name;
//    }
}

SendWelcomeEmailMessageHandler

<?php

namespace App\MessageHandler;

use App\Message\SendWelcomeEmailMessage;
use Symfony\Component\Messenger\Handler\MessageHandlerInterface;

class SendWelcomeEmailMessageHandler implements MessageHandlerInterface
{
    public function __invoke(SendWelcomeEmailMessage $message)
    {
        // do something with your message
    }
}

In the future... we could possibly ask which transport you want to use and update your YAML configuration (if needed) 🤔

[OskarStark]

what about doing it like in the make entity command, one could nearly reuse the existing code without the annotations stuff. This would make it more handy imo

[LiSinCin]

Hi, can you point what part of command or entity can be reused? :)

[OskarStark]

would you mind making this final?

[OskarStark]

final, too?

[rvanlaak]

Would be preferable to keep messages immutable. What about not promoting setters?

[OskarStark]

Good idea 💡

[weaverryan]

I agree to remove the setter example

[weaverryan]

this comment can now be removed

[weaverryan]

I agree to remove the setter example

[nikophil]

Hi,

according to a chat i had with @weaverryan i've completed this maker in order to allow the user to route the message to a transport

[OskarStark]

I am routing my Messages based on an „AsyncMessage“-Marker Interface, is it worth to add such an option instead of manipulating the messenger.yaml file?

[weaverryan]

It’s a very interesting idea... but I don’t think it’s standard enough yet to put into maker. Better to show them where/how routing happens

[nikophil]

i kinda agree with @weaverryan. Although it is a nice trick, it may involve too much complexity and different cases to handle in the maker.

BTW, the CI is failing because of some deprecation i fixed here: #518

[weaverryan]

Thank you for taking this across the finish line @nikophil!

[OskarStark]

Nice, when can we expect a release? 😊😎

[weaverryan]

Soon! Finishing the new reset password stuff!