Package Data | |
---|---|
Maintainer Username: | rafflesargentina |
Maintainer Contact: | mario@raffles.com.ar (Mario Patronelli) |
Package Create Date: | 2017-12-27 |
Package Last Update: | 2020-06-24 |
Language: | PHP |
License: | MIT |
Last Refreshed: | 2024-12-16 15:01:05 |
Package Statistics | |
---|---|
Total Downloads: | 243 |
Monthly Downloads: | 0 |
Daily Downloads: | 0 |
Total Stars: | 3 |
Total Watchers: | 2 |
Total Forks: | 1 |
Total Open Issues: | 0 |
A trait for filtering and sorting Query Builder strings, based on Laracasts/Dedicated-Query-String-Filtering.
Via Composer
$ composer require rafflesargentina/l5-filterable-sortable
Add FilterableSortableTrait to your Eloquent model so you can make use of filter() and sorter() scopes. Both apply clauses to the Builder intance that you must define as functions in separate classes. So you must add $filters and $sorters properties to your model to set those classes.
Example:
<?php
namespace App\Models;
use Illuminate\Database\Eloquent\Model;
use RafflesArgentina\FilterableSortable\FilterableSortableTrait;
use App\Filters\ArticleFilters;
use App\Sorters\ArticleSorters;
class Article extends Model
{
use FilterableSortableTrait;
public $filters = ArticleFilters::class;
public $sorters = ArticleSorters::class;
// ...
}
Create a class that extends QueryFilters and define methods named after each request data you want to use as a chained query filter. You can employ any logic inside functions, as long as they return a Builder instance.
Example:
<?php
namespace App\Filters;
use RafflesArgentina\FilterableSortable\QueryFilters;
class ArticleFilters extends QueryFilters
{
public function title($query)
{
return $this->builder->where('title', 'LIKE', '%'.$query.'%');
}
public function author($query)
{
return $this->builder->where('user_id', $query);
}
public function category_id($query)
{
return $this->builder->where('category_id', $query);
}
}
You can also access the class method getAppliedFilters() statically, to get an array of the filters applied from request.
Create a class that extends QuerySorters, and define public methods named after each request data you want to use as a chained query sorter. You can employ any logic inside functions, as long as they return a Builder instance. Default order and default orderBy must be set through $defaultOrder and $defaultOrderBy static properties. Optionally you can define order and orderBy keys through $orderKey and $orderByKey static properties.
Example:
<?php
namespace App\Sorters;
use RafflesArgentina\FilterableSortable\QuerySorters;
class ArticleSorters extends QuerySorters
{
// These properties are optional:
protected static $orderKey = 'orden'; // Fallback value is 'order'
protected static $orderByKey = 'ordenarPor'; // Fallback value is 'orderBy'
// And there are mandatory:
protected static $defaultOrder = 'asc';
protected static $defaultOrderBy = 'title';
public function title()
{
return $this->builder->orderBy('title', $this->order());
}
public function published_at()
{
return $this->builder->orderBy('updated_at', $this->order())
->orderBy('title', $this->order());
}
}
Also you can access these static class methods to get sorter class protected data: getOrderKey(), getOrderByKey(), getDefaultOrder(), getDefaultOrderBy(). Use getAppliedSorters() to get applied sorters from request. Or listOrderByKeys() to populate a dropdown selector.
You can get filtered and sortered records from your model from controller or anywhere you want like this:
// ...
$items = Article::filter()->sorter()->paginate();
// ...
That's it :)
$ composer test
Please see CONTRIBUTING and CONDUCT for details.
If you discover any security related issues, please email mario@raffles.com.ar instead of using the issue tracker.
The MIT License (MIT). Please see License File for more information.