Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/andanteproject/page-filter-form-bundle
A Symfony Bundle to simplify the handling of page filters for lists/tables in admin panels.
https://github.com/andanteproject/page-filter-form-bundle
admin-panel admin-panels filter-form filters form page-filters php php7 php74 symfony symfony-bundle symfony-form
Last synced: about 1 month ago
JSON representation
A Symfony Bundle to simplify the handling of page filters for lists/tables in admin panels.
- Host: GitHub
- URL: https://github.com/andanteproject/page-filter-form-bundle
- Owner: andanteproject
- License: mit
- Created: 2021-03-12T18:22:51.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-07-29T10:54:26.000Z (4 months ago)
- Last Synced: 2024-09-29T20:01:29.894Z (about 2 months ago)
- Topics: admin-panel, admin-panels, filter-form, filters, form, page-filters, php, php7, php74, symfony, symfony-bundle, symfony-form
- Language: PHP
- Homepage:
- Size: 50.8 KB
- Stars: 8
- Watchers: 3
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Page Filter Form Bundle
#### Symfony Bundle - [AndanteProject](https://github.com/andanteproject)
[](https://github.com/andanteproject/page-filter-form-bundle/releases)
A Symfony Bundle to simplify the handling of page filters for lists/tables in admin panels. 🧪
## Requirements
Symfony 4.x-7.x and PHP 7.4-8.0.
## Features
- Use [Symfony Form](https://symfony.com/doc/current/forms.html);
- Keep you URL parameters clean as `?search=value&otherFilterName=anotherValue` by default;
- Form will work even if you render form elements **outside the form tag**, around the web page, exactly where you need,
**avoiding nested form conflicts**.
- Super easy to implement and maintains;
- Works like magic ✨.
## How to install
After [install](#install), make sure you have the bundle registered in your symfony bundles list (`config/bundles.php`):
```php
return [
/// bundles...
Andante\PageFilterFormBundle\AndantePageFilterFormBundle::class => ['all' => true],
/// bundles...
];
```
This should have been done automagically if you are using [Symfony Flex](https://symfony.com/components/Symfony%20Flex). Otherwise, just
register it by yourself.
## The problem
Let's suppose you have this common admin panel controller with a page listing some `Employee` entities.
```php
getFancyQueryBuilderLogic('employee');
$employees = $paginator->paginate($qb, $request);
return $this->render('admin/employee/index.html.twig', [
'employees' => $employees,
]);
}
}
```
To add filters to this page, let's create a Symfony form.
```php
add('search', Type\SearchType::class);
$builder->add('senior', Type\CheckboxType::class);
$builder->add('orderBy', Type\ChoiceType::class, [
'choices' => [
'name' => 'name',
'age' => 'birthday'
],
]);
}
}
```
Let's add this Form to our controller page:
```php
getFancyQueryBuilderLogic('employee');
$form = $this->createForm(EmployeeFilterType::class);
$form->handleRequest($request);
if($form->isSubmitted() && $form->isValid()){
$qb->expr()->like('employee.name',':name');
$qb->setParameter('name', $form->get('search')->getData());
$qb->expr()->like('employee.senior',':senior');
$qb->setParameter('senior', $form->get('senior')->getData());
$qb->orderBy('employee.'. $form->get('orderBy')->getData(), 'asc');
// Don't you see the problem here?
}
$employees = $paginator->paginate($qb, $request);
return $this->render('admin/employee/index.html.twig', [
'employees' => $employees,
'form' => $form->createView()
]);
}
}
```
The code above has some huge problems:
- 👎 Handling all this filter logic inside the controller is not a good idea. Sure, you can move it inside a dedicated
service, but this means we are creating another file class alongside `EmployeeFilterType` to handle filters and this
is not even solving this list's the second point;
- 👎 You need to carry around and match form elements names. `search`, `senior` and `orderBy` are keys you could store
in some constants to don't repeat yourself, but this will drive you crazy as the filter logic grows.
## The solution with Page Filter Form
Use `Andante\PageFilterFormBundle\Form\PageFilterType` as parent of your filter
form ([why?](#why-use-pagefiltertype-as-from-parent)) and implement `target_callback` option on your form elements like
this:
```php
add('search', Type\SearchType::class, [
'target_callback' => function(QueryBuilder $qb, ?string $searchValue):void {
$qb->expr()->like('employee.name',':name'); // Don't want to guess for entity alias "employee"?
$qb->setParameter('name', $searchValue); // Check andanteproject/shared-query-builder
}
]);
$builder->add('senior', Type\CheckboxType::class, [
'target_callback' => function(QueryBuilder $qb, bool $seniorValue):void {
$qb->expr()->like('employee.senior',':senior');
$qb->setParameter('senior', $seniorValue);
}
]);
$builder->add('orderBy', Type\ChoiceType::class, [
'choices' => [
'name' => 'name',
'age' => 'birthday'
],
'target_callback' => function(QueryBuilder $qb, string $orderByValue):void {
$qb->orderBy('employee.'. $orderByValue, 'asc');
}
]);
}
public function getParent() : string
{
return PageFilterType::class;
}
}
```
Implement `Andante\PageFilterFormBundle\PageFilterFormTrait` in you controller (or inject an
argument `Andante\PageFilterFormBundle\PageFilterManagerInterface` as argument) and use form like this:
```php
getFancyQueryBuilderLogic('employee');
$form = $this->createAndHandleFilter(EmployeeFilterType::class, $qb, $request);
$employees = $paginator->paginate($qb, $request);
return $this->render('admin/employee/index.html.twig', [
'employees' => $employees,
'form' => $form->createView()
]);
}
}
```
✅ Done!
- 👍 Controller is clean and easy to read;
- 👍 We have just one class taking care of filters;
- 👍 The option `target_callback` allows you to not repeat yourself carrying around form elements names;
- 👍 You can type-hint you callable 🥰 ([check callback arguments](#target_callback-option));
- 👍 We got you covered solving possible nested form problems ([how?](#render-the-form-in-twig));
### "target_callback" option
#### target_callback
**type**: `null` or `callable` **default**: `null`
The `callable` is going to have 3 parameters (third is optional):
| Parameter | What | Mandatory | Description |
| --------- | ---- | --------- | ----------- |
| 1 | Filter `$target` | `yes` | It's the second argument of `createAndHandleFilter`. It can be whatever you want: a query builder, an array, a collection, a object. It doesn't matter as long you match it's type with this argument sign. |
| 2 | form data | `yes` | Equivalent to call `$form->getData()` on the current context. It is going to be a `?string` on a `TextType` or a `?\DateTime` on a `DateTimeType` |
| 3 | form itself | `no` | It's the current `$form` itself. |
### Why use PageFilterType as from Parent
You could avoid to use `Andante\PageFilterFormBundle\Form\PageFilterType` as parent for your form, but be aware it sets
some useful default you may want to replicate:
| Option | Value | Description |
| --- | --- | --- |
| `method` | `GET` | You probably want filters to be part of the URL of the page, don't you? |
| `csrf_protection` | `false` | You want the user to be able to share the URL of the page to another user without facing problems |
| `allow_extra_fields` | `true` | Allow other URL parameters outside your form values |
| `andante_smart_form_attr` | `true` | Enable form elements rendering wherever you want inside you page, even outside form tag while keeping them working properly ([discover more](https://www.w3schools.com/html/html_form_attributes_form.asp)). |
### Render the form in twig
As long as `andante_smart_form_attr` is `true`, you can render your form like this:
```twig
{{ form_start(form) }} {# id="list_filter" #}
{{ form_errors(form) }}
{{ form_row(form.search) }}
{{ form_row(form.orderBy) }}
{{ form_end(form, {'render_rest': false}) }}
```
✅ `form.perPage` element work properly even outside form tag ([how?!](https://www.w3schools.com/html/html_form_attributes_form.asp)).
Give us a ⭐!
Built with love ❤️ by [AndanteProject](https://github.com/andanteproject) team.