Download the PHP package polysource/easyadmin-filter-bridge without Composer

polysource/easyadmin-filter-bridge

Drop-in package that enriches the filters of an existing EasyAdmin app (4.24+ or 5.0+) without forking EasyAdmin. Plugs into EasyAdmin's FilterConfiguratorInterface extension point.

Status

v1.1.0 published (2026-08-07). The public API is frozen under strict SemVer since v1.0.0 (2026-08-06) — breaking changes only in a new major (cf. ADR-012). Distributed on Packagist as polysource/easyadmin-filter-bridge.

Feature-complete on the bridge side, dogfooded on multi-tenant client integrations since v0.5.7:

• All 8 built-in EasyAdmin filters covered by an Enhancer (DateTime, Boolean, Text, Numeric, Choice, Comparison, Array, Entity).
• 4 custom filter types: BetweenDateFilter, InFilter, NotNullFilter, FullTextSearchFilter.
• Twig templates auto-register via PrependExtensionInterface — enhanced widget HTML renders with zero config.
• Filter session persistence via FilterSessionPersistenceSubscriber on BeforeCrudActionEvent — operators returning to the index page see their previous filters restored automatically (scoped per CRUD controller FQCN, no leak across resources).
• Expandable row details since v1.1.0 — opt in per entity with a RowDetailProviderInterface implementation (3 methods: getSupportedEntity / getPermission / getRowDetail), or extend AbstractRowDetailProvider and write only getSupportedEntity() + template(). Then add the bridge's Polysource::rowDetail() field (Polysource\EasyAdminFilterBridge\Bridge\Polysource) to configureFields() and each row gains a chevron that lazily loads its panel. No table_body_row fork — it is a virtual EA field, identical on EA 4.24 and 5.x.
• 9 polysource routes auto-import via Bundle::boot() since v0.5.4 — no manual routes.yaml import needed in the host.
• Multi-kernel safe since v0.5.7 — bundle is a no-op on EA-less kernels.
• Multi-tenant ready since v0.5.7 — opt out of auto-route registration via auto_register_routes: false to mount under a custom prefix (e.g. /{channel}/admin).

What it does

Once installed, EasyAdmin's built-in filters gain richer form types, without any change to your existing CRUD controllers:

Plus, list-level capabilities layered on top:

• Filter chips/tags bar above the table (active filters visible, click X to remove).
• Session persistence of filters per CRUD controller FQCN.
• Saved views dropdown (private / team / public scopes).
• Column visibility dropdown + column reordering.
• Filter-aware streaming export (CSV / XLSX).
• Matching-count JSON endpoint for bulk dry-run preview.
• Filter URL tokens for short shareable filtered URLs.
• Expandable row details — a per-row chevron that lazily fetches GET /admin/polysource/row-detail/{resource}/{id}. The provider's permission attribute is checked with the row's entity as voter subject (fail-closed), so a panel one operator may open stays shut for another. Without JavaScript the chevron is a plain link to the same URL, which renders a standalone page.
• Custom filter types: BetweenDateFilter, InFilter, NotNullFilter, FullTextSearchFilter.

A provider returns a RowDetail (from polysource/core), and it has two shapes. RowDetail::template() renders your own Twig and needs nothing beyond this bundle. RowDetail::listing() embeds another Polysource resource as the panel — a nested, paged, read-only table — and that renderer lives in polysource/symfony-bundle, so install it alongside the bridge if you want the listing shape.

Installation

The bundle auto-registers via Symfony Flex. If you don't use Flex, add it manually to config/bundles.php:

Zero configuration needed. As soon as the bundle is loaded, the shipped Configurators auto-tag themselves via EasyAdmin's registerForAutoconfiguration(FilterConfiguratorInterface::class), and EasyAdmin's FilterFactory picks them up to mutate filter DTOs right after they are created.

Frontend assets — server-rendered first, Stimulus optional

The filter modal tabs, group accordions, and the chips bar are server-rendered — zero JavaScript required (since v0.2.0, per ADR-027 progressive enhancement). Tabs use native <details name="..."> exclusive accordions, pane switching is pure CSS, and every chip's × button is a plain link.

Two kinds of assets ship with the bundle:

1. A stylesheet + a small defensive script in Resources/public/, published to public/bundles/polysourceeasyadminfilterbridge/ by assets:install (Symfony Flex runs it automatically). The bridge's index template links them itself — nothing to wire. Theming is done through --polysource-* CSS variables — see the theming guide.
2. Two optional Stimulus controllers. polysource--filter ships here (assets/controllers/) and progressively enhances the filter widgets: preset buttons, quick-ranges, clear buttons, validation hints. polysource--row-details drives the row-detail panel (loading / error / retry states, client-side cache, ARIA) and ships from polysource/filter — the same controller the native polysource/symfony-bundle listing uses, so there is one implementation, not two. Hosts using AssetMapper or Webpack Encore
   • StimulusBundle get both auto-loaded via the assets/package.json advertisements; hosts without any JS pipeline simply keep the server-rendered behaviour.

If you use AssetMapper, remember EasyAdmin ignores the host importmap by default — add it back via your Dashboard so the optional controller boots on admin pages:

Saved views (POST routes)

polysource/filter ships a saved-views feature (dropdown, save, load, delete). The bridge wires the create / delete routes for EasyAdmin out of the box — they live at:

• POST /admin/saved-views (polysource_saved_view_create)
• POST /admin/saved-views/{id}/delete (polysource_saved_view_delete)

They are auto-imported — along with the 7 other polysource_* routes — by Bundle::boot() since v0.5.4, so no routes.yaml change is needed. Multi-tenant hosts mounting EA under a custom prefix can opt out with auto_register_routes: false and import @PolysourceEasyAdminFilterBridge/Resources/config/routes.php under their own prefix instead.

A BeforeCrudActionEvent subscriber also expands ?view=<id> into the EA filters[...]=... query and redirects to a clean URL — no host code needed.

Quick start

Take any existing EasyAdmin CRUD controller:

After installing this bridge, the same code automatically:

• The createdAt filter renders with the enhanced datetime form type (dedicated block prefix for theme overrides) instead of the stock date picker.
• The isActive filter accepts an include_null option (default false) to show a third "Null" radio choice when the column is nullable.

To opt-in to per-resource overrides, pass formTypeOptions to the upstream filter:

How the seam works

No EasyAdmin code is modified. We only attach more services to the existing extension point.

The full audit trail of seams used (and one that is not available — the EntityRepositoryInterface returns Doctrine\ORM\QueryBuilder, which blocks non-Doctrine sources) is in ADR-012 §Vérification technique.

Writing your own enhancer

Want to add a custom Configurator (e.g. a richer TextFilter with mode-toggle "exact / starts-with / contains")? The pattern is small:

With Symfony's autowiring + autoconfiguration (default), it gets auto-tagged ea.filter_configurator. Done. No service.yaml entry, no compiler pass, no fork.

Testing

Unit tests live in tests/Unit/Configurator/ — they instantiate real FilterDto instances (not mocks), run our supports() + configure(), and assert the DTO mutations. EntityDto and AdminContext are final in EasyAdmin v5, so the tests use (new ReflectionClass(...))->newInstanceWithoutConstructor() to satisfy the typehints without coupling to internal shape — the Configurators never read either argument.

Compatibility

Cf. ADR-015 — multi-version baseline; CI runs the full matrix.

• PHP >=8.2
• Symfony ^6.4 || ^7.0 || ^8.0
• EasyAdmin ^4.24 || ^5.0
• Doctrine ORM ^2.20 || ^3.0

Architectural decisions

• ADR-012 — Dual-product positioning — why this bridge exists alongside the standalone product.
• ADR-016 — Bridge contracts shared with polysource/filter — the ChipFormatterInterface boundary between the bridge and the standalone primitive.
• ADR-033 — Expandable row details — the virtual-field seam, the lazy fragment endpoint, and the no-JS page.

License

MIT — see LICENSE.