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.

3.7.10

Fix styling

3.7.9: release create :wq

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

3.7.8

Fixed

• Log when an unserialize error occurs for MailatorScheduler.

3.7.7

Fixed

• Queue config name: #2555

3.7.6

Fixed

• Fix logs #2554

3.7.5

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

3.7.4

Added

• executeWhenPasses method on MailatorScheduler so now executions will take into consideration constraints
• Added Binarcode\LaravelMailator\Scheduler and Binarcode\LaravelMailator\Mailator facades so you can use:

Scheduler::init('Reminder')
->mailable(new Mailable())
->hours(1)
->before(Carbon::parse($someDate))

You don't even need to save it, as the package knows to save this pending instance when the script ends.