Bot releases are hidden (Show)
$column->value()
method (https://github.com/Okipa/laravel-table/issues/54).button
method without arguments has no visual effect: added instructions in V2 to v3 the upgrade-guide to take care of this new behaviour.rows number definition
was wrongly named rows number selection
at different places (config, templates, methods, ...): this is an unfortunately breaking change if you published config or templates but I take advantage of the early release of the V3 and from the fact that Laravel 8 is not released to do it.GET
http request.Table
instances :
rowsSearchingTemplate
rowsNumberSelectionTemplate
createActionTemplate
columnTitlesTemplate
navigationStatusTemplate
paginationTemplate
show
, edit
and destroy
actions are now defined in their own component. This way, it becomes easier to customize tiny parts of the table without touching to the others.
config('laravel-table.template.show')
, config('laravel-table.template.edit')
and config('laravel-table.template.destroy')
configs to set each new default component path.->showTemplate()
, ->editTemplate()
and ->destroyTemplate()
to give the ability to customize these templates on the fly.php artisan vendor:publish --tag=laravel-table:translations
php artisan vendor:publish --tag=laravel-table:config
php artisan vendor:publish --tag=laravel-table:views
--prefer-lowest
composer tag to check the package compatibility with the lowest dependencies versions).show
, edit
and destroy
routes generation instead of its id.// assuming your declared your edit route like this :
(new Table)->model(User::class)->routes([
// ...
'edit' => ['name'=> 'user.edit', 'params' => ['foo' => 'bar']],
//...
])
// the route will be generated like this during the table instantiation :
route('user.edit, [$user, 'foo' => 'bar']);
// instead of this way
route('user.edit, [$user->id, 'foo' => 'bar']);
// with a route declared like this :
Route::get('user/edit/{user}/{foo}', 'UsersController@edit')->name('user.edit');
// and a table routes declaration like this :
(new Table)->model(User::class)->routes([
// ...
'edit' => ['name'=> 'user.edit', 'params' => ['bar']],
//...
])
// the route is now correctly generated and gives : /user/edit/1/bar instead of /user/edit/bar/1
show
, edit
and destroy
route generation, since Laravel 6 does handle differently the key given in the route()
helper call :// assuming your declared your edit route like this :
(new Table)->model(User::class)->routes([
// ...
'edit' => ['name'=> 'user.edit', 'params' => ['foo' => 'bar']],
//...
])
// the route will be generated like this during the table instantiation :
route('user.edit, [$user->id, 'foo' => 'bar']);
// instead of this way
route('user.edit, ['id' => $user->id, 'foo' => 'bar']);
->identifier('your identifier')
. This identifier will be used for several things :
rows
, search
, sort_by
, sort_dir
.