Wallogit.com
2017 © Pedro Peláez
Listing Bundle providing easy datatables (http://www.datatables.net/) usage
, (*1)
Data tables listing plugin allow you to easy creating record list, using Symfony forms style. This plugin use popular JQuery DataTables plug (http://www.datatables.net/), (*2)
{
"pawellen/data-tables-listing": "dev-master"
}
$bundles = array (
(...)
new PawelLen\DataTablesListing\DataTablesListingBundle()
);
2,5. Configuration:
data_tables_listing:
default_template: LenPanelBundle::listing_div_layout.html.twig
include_assets:
datatables_js: false
datatables_css: false
include_jquery: false
jquery_js: "//code.jquery.com/jquery-2.1.3.min.js"
3. Add DataTables javascript script to your template using listing_scripts twig function.
Example:
```html
<html>
<head>
(...)
<script src="{{ asset('bundles/exapmlebundle/js/jquery/jquery.min.js') }}" type="text/javascript"></script>
{{ listing_scripts() }}
(...)
</head>
<body>
(...)
</body>
</html>
To create listing you just need to get listing service in your controller and pass to it your listing type object. Example:, (*3)
/**
* @Route("/user/list")
* @Template()
*/
public function listAction(Request $request)
{
// Creates new listing object:
$list = $this->get('listing')->createListing(new UserListing(), array(
'request' => $request
));
// Handle ajax request that provide data to listing:
if ($request->isXmlHttpRequest()) {
return $list->createResponse($request);
}
// Pass ListView object to your template:
return array(
'list' => $list->createView()
);
}
As you can see usage of listing is very similar to Symfony forms component. As one of options passed to createListing method is Request object. Request object is used to get any data passed form your site, for example filters, column order by itp..., (*4)
Creating new listing type looks similar like creation of symfony form. Example:, (*5)
namespace Td\UserBundle\Listing;
use PawelLen\DataTablesListing\Type\AbstractType;
use PawelLen\DataTablesListing\Filters\FilterBuilderInterface;
use PawelLen\DataTablesListing\Listing\ListingBuilderInterface;
class UserListing extends AbstractType
{
public function buildFilters(FilterBuilderInterface $builder, array $options)
{
$builder->add('name', 'text', array(
'label' => 'User name',
'required' => false,
'filter' => array(
'property' => 'name',
'expression' => 'c.name LIKE :name'
)
));
$builder->add('email', 'text', array(
'label' => 'Email',
'required' => false,
'filter' => array(
'expression' => 'c.shortName LIKE :shortName'
)
));
}
public function buildListing(ListingBuilderInterface $builder, array $options)
{
$builder->add('id', 'column', array(
'label' => 'Id'
));
$builder->add('name', 'column', array(
'label' => 'User name'
));
$builder->add('email', 'column', array(
'label' => 'Email'
));
}
public function setDefaultOptions(OptionsResolverInterface $resolver)
{
$resolver->setDefaults(array(
'class' => 'TdUserBundle:User'
));
}
public function getName()
{
return 'my_list';
}
}
This will create listing of users with two filter fields and three columns. Data source is pointed in setDefaultOptions method. Instead of single entity passed in "class" option you can use also option query_builder and provide query builder interface to access more complicated query with joins., (*6)
To render created listing, you must pass ListingView object to your template: Example:, (*7)
{% extends "PanelBundle::base_template.html.twig" %}
{% form_theme list.filters _self %}
{% block _my_list_widget %}
{{ form_row(form.name) }}
{{ form_row(form.email) }}
{% endblock _my_list_widget %}
{% block content_body %}
{{ listing(list) }}
{% endblock %}
To render entire listing, you can use listing() twig function. This example shows also how to overwrite filters template. Notice that there is a leading underscore in block name., (*8)
To create link you need to add link option inside buildListing method., (*9)
$builder->add('name', 'column', array(
'label' => 'User name',
'link' => array(
'route' => 'user_edit',
'params' => array(
'user_id' => 'id'
)
)
));
where: id is a propertyPath string. route is a route name params are parameters to generateUrl function, (*10)
To use query builder you need to use query_builder option instead of class., (*11)
public function setDefaultOptions(OptionsResolverInterface $resolver)
{
$resolver->setDefaults(array(
'query_builder' => function(QueryBuilder $builder) {
$builder->select('u, a, t')
->from('TdUserBundle:Contractor', 'u')
->leftJoin('u.address', 'a')
->leftJoin('u.type', 't')
->where('u.deletedAt IS NULL');
}
));
}
or, (*12)
public function setDefaultOptions(OptionsResolverInterface $resolver)
{
$resolver->setDefaults(array(
'class' => 'TdUserBundle:User',
'query_builder' => function(EntityRepository $er) {
return $er->createQueryBuilder('u')
->where('u.deletedAt IS NULL');
}
));
}
By default, when building filters form you don't need to define any filters, you may pass empty array as filter options, in this case default search will be performed. Default search use "name LIKE %PHRASE%" sql query, where name is filter name and PHRASE is the value of input. To use custom filter just pass the DQL expression to filter option. Example:, (*13)
$builder->add('name', 'text', array(
'label' => 'User name',
'required' => false,
'filter' => array(
'expression' => 'u.name LIKE :name',
'eval' => '%like%'
)
))
where: expression is a DQL expression, You can use parameter multiple times, for example: "u.firstname LIKE :name OR u.lastname LIKE :name". eval is not required parameter it is used to modify value passed from filter form, (*14)
notice: :name MUST be always same as filter name (in current version), (*15)
In some cases your listing is very simple but there is case when you use some filters you have to add some complicated joins, but in other cases you don't want apply that joins to query because they are very expensive. Example:, (*16)
```php $builder->add('languageCode', 'text', array( 'label' => 'Language code', 'required' => false, 'filter' => array( 'expression' => 'l.code LIKE :languageCode', 'eval' => '%like%', 'query_builder' => function(QueryBuilder $builder) { $builder->addSelect('l') ->join('c.language', 'l'); } ) )), (*17)
In this example when user fill "Language code" filter, ***join('c.language')*** will be added and languageCode condition will be added to query. ***Deprecated*** parameter joins (used in old version): ```php // DEPRECATED: $builder->add('country', 'text', array( 'label' => 'Country name', 'required' => false, 'filter' => array( 'expression' => 'c.name LIKE :country', 'eval' => '%like%', 'join' => array( array('field' => 'u.address', 'alias' => 'a'), array('field' => 'a.country', 'alias' => 'c'), ) ) ))
In this case country will be joined only if country filter is passed by user, otherwise joins are not used., (*18)
Inside buildListing method you can add action buttons to your list position. Example:, (*19)
->add('edit', 'button', array(
'label' => 'Edit',
'route' => 'user_edit',
'params' => array(
'contractor_id' => 'id'
)
))
When you need dynamically modify/extend table rows or filters search criteria you can use one of listing events., (*20)
When using query_bulder you can use option property to access any data from fetched entity. For example: If you have related entity you can can access its getter threw property accessor:, (*21)
$builder->add('status', 'text', array(
'label' => 'Status',
'property' => 'status.name',
));
or you can even can access first object in collection:, (*22)
$builder->add('user', 'text', array(
'label' => 'First user',
'property' => 'users[0].name',
));
listing allow you tu use some magic wildcard **[]***, to collect all values in collection and display it as coma separated string:, (*23)
$builder->add('user', 'text', array(
'label' => 'Users',
'property' => 'users[*].name',
));
NOTE: You can use onlu one wildcard in your property option., (*24)
Listing Bundle providing easy datatables (http://www.datatables.net/) usage
Apache2
datatables listing