Laravel Mail Editor Versions Save

What's Changed

• Update composer.json to support Laravel 10 by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/233

Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v4.0.5...v4.1.0-beta.0

Fixes

• Lines variable needs to be array and not integer for loadNamespaceOverrides method. by @nicoorfi in https://github.com/Qoraiche/laravel-mail-editor/pull/231
• Apply fixes from StyleCI by @Qoraiche in https://github.com/Qoraiche/laravel-mail-editor/pull/232

Dependabot

• Bump engine.io and browser-sync by @dependabot in https://github.com/Qoraiche/laravel-mail-editor/pull/222
• Bump socket.io-parser and browser-sync by @dependabot in https://github.com/Qoraiche/laravel-mail-editor/pull/217

New Contributors

• @nicoorfi made their first contribution in https://github.com/Qoraiche/laravel-mail-editor/pull/231

Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v4.0.4...v4.0.5

What's Changed

• Fix/route errors by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/212
• fix: compatible way to call the method on mailable by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/219

Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v4.0.3...v4.0.4

What's Changed

• Update mailables.blade.php by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/202

Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v3.5.2...v3.5.3

What's Changed

• Fix for issue #199, syntax error by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/200
• Update versions for latest fix by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/201

Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v4.0.2...v4.0.3

Thank you to @AliKHODR

With this addition, please make use of the updated config values in config/maileclipse.php. You need to add the following

    /*
    |--------------------------------------------------------------------------
    | Display Mailable Subject
    |--------------------------------------------------------------------------
    |
    | Set to true this will display the subject of the Mailable instead of Class Name.
    | When the config setting is false the namespace/class name is shown
    | options: true / false
    |
    */
    'display_as_subject' => true,

What's Changed

• Merge Master into v3.x branch in https://github.com/Qoraiche/laravel-mail-editor/pull/193
• [3.x] Feature/change table names issue 79 in https://github.com/Qoraiche/laravel-mail-editor/pull/194
• Merge v3 updates in https://github.com/Qoraiche/laravel-mail-editor/pull/198

Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v4.0.1...v4.0.2

This adds improved feedback about the usage of factories when the option is enabled in the config file and none are found for a model.

What's Changed (Auto-generated)

• Refac/improve error handling and feedback by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/196

Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v4.0.0...v4.0.1

Added

• Adds the subject of the email client to the table instead of the namespace. See Issue #79, PR #194

Please add the following to the config/maileclipse.php file to be able to toggle the settings for this added feature.

    /*
    |--------------------------------------------------------------------------
    | Display Mailable Subject
    |--------------------------------------------------------------------------
    |
    | Set to true this will display the subject of the Mailable instead of Class Name.
    | When the config setting is false the namespace/class name is shown
    | options: true / false
    |
    */
    'display_as_subject' => true,

Fix

• Correct custom Mailable directory usage from config, see PR #190 @Bhagyrajaj

Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v3.5.1...v3.5.2

Add Laravel 9 support: See PR https://github.com/Qoraiche/laravel-mail-editor/pull/191

Fixes

• Fixes an issue where in some cases Faker data would cause a issue for the javascript frontend. See #187 and #188