invoiceninja/resources/views/vendor/mail/html/header.blade.php

<tr>
<td class="header">
<a href="{{ $url }}">
{{ $slot }}
</a>
</td>
</tr>
Datatables using Vue (#2568) * Vue DataTables * Vue Datatables - Pagination * Sort Vue Tables * Working on Vue Datatables * Apply filter to vue table * Search implementation for vue datatables * Clean up 2018-12-24 01:45:55 +01:00			`<tr>`
Laravel 7.x Shift (#40) * Adopt Laravel coding style The Laravel framework adopts the PSR-2 coding style with some additions. Laravel apps should adopt this coding style as well. However, Shift allows you to customize the adopted coding style by adding your own [PHP CS Fixer][1] `.php_cs` config to your project. You may use [Shift's .php_cs][2] file as a base. [1]: https://github.com/FriendsOfPHP/PHP-CS-Fixer [2]: https://gist.github.com/laravel-shift/cab527923ed2a109dda047b97d53c200 * Shift bindings PHP 5.5.9+ adds the new static `class` property which provides the fully qualified class name. This is preferred over using class name strings as these references are checked by the parser. * Shift core files * Shift to Throwable * Add laravel/ui dependency * Unindent vendor mail templates * Shift config files * Default config files In an effort to make upgrading the constantly changing config files easier, Shift defaulted them so you can review the commit diff for changes. Moving forward, you should use ENV variables or create a separate config file to allow the core config files to remain automatically upgradeable. * Shift Laravel dependencies * Shift cleanup * Upgrade to Laravel 7 Co-authored-by: Laravel Shift <shift@laravelshift.com> 2020-09-06 11:38:10 +02:00			`<td class="header">`
			`<a href="{{ $url }}">`
			`{{ $slot }}`
			`</a>`
			`</td>`
Datatables using Vue (#2568) * Vue DataTables * Vue Datatables - Pagination * Sort Vue Tables * Working on Vue Datatables * Apply filter to vue table * Search implementation for vue datatables * Clean up 2018-12-24 01:45:55 +01:00			`</tr>`