3.11.1

Merge branch '3.x' of github.com:BinarCode/laravel-mailator into 3.x

3.11.0

Added

• Support for Laravel 9

3.10.0

Added

Events

Mailator has few events you can use.

If your mailable class extends the Binarcode\LaravelMailator\Contracts\Beforable, you will be able to inject the before method, that will be called right before the sending the email.

If your mailable class extends the Binarcode\LaravelMailator\Contracts\Afterable, you will be able to inject the before method, that will be called right after the mail has being sent.

And latest, after each mail has being sent, mailator will fire the Binarcode\LaravelMailator\Events\ScheduleMailSentEvent event, so you can listen for it.

3.9.4

Merge branch '3.x' of github.com:BinarCode/laravel-mailator into 3.x

3.9.3

Filter out myself when saving

3.9.2

Ensure doesn't send unique twice

3.9.1

Merge branch '3.x' of github.com:BinarCode/laravel-mailator into 3.x

3.9.0

Unique

You can configure your scheduler to store a unique relationship with the target class for mailable by specifying:

->unique()

ie:

Scheduler::init()
    ->mailable(new InvoiceReminderMailable())
    ->target($user)
    ->unique()
    ->save();
    
Scheduler::init()
    ->mailable(new InvoiceReminderMailable())
    ->target($user)
    ->unique()
    ->save();

To migrate on this version, add a migration to add:

        Schema::table('mailator_schedulers', function (Blueprint $table) {
            $table->boolean('unique')->default(false);
        });

3.8.1

Added

• immediate readable condition

3.8.0

Added

• stopable() scheduler method which ensure that if the constraints didn't pass at a certain time, the mail will be considered completed. This way it will be much more performant.
• Improved documentation
• Improved Garbadge collector and command.
• Added run command for the Scheduler facade.