You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today the FilterBundle is part of victoire and have only one purpose.
He provide some base class to facilitate the creatio of Filter class.
Filter class who are only use in conjunction with the widget filter and listings.
The first issue with that, is the fact that we have an business stack that will
never interact with victoire and is bnudle, unneless with the right widget. This logic
shouldn't be located directly in this widget.
The second being the structure of the Filter class, they all implement to method buildForm
and buildQuery.
bundleForm make sens since this class is based on the AbstractType class from symfony.
But buildQuery is called to construct the query who will bring the result of the filter action on the filter widget.
Then we should conserve the filter class for the widget filter content resolver need who are to display a form.
And create a new type of class filter who are made to talk with widget listing content resolver in order
to filtrate the list.
Resolution Ideas
Dont no yet
Related to
Bundle
--
--
--
Analytics
✔
Page
✔
Blog
Query
BusinessEntity
Seo
BusinessPage
Sitemap
Core
Template
Criteria
Twig
Filter
X
User
Form
ViewReference
I18n
Widget
Media
WidgetMap
UI
The text was updated successfully, but these errors were encountered:
Description
Today the FilterBundle is part of victoire and have only one purpose.
He provide some base class to facilitate the creatio of Filter class.
Filter class who are only use in conjunction with the widget filter and listings.
The first issue with that, is the fact that we have an business stack that will
never interact with victoire and is bnudle, unneless with the right widget. This logic
shouldn't be located directly in this widget.
The second being the structure of the Filter class, they all implement to method buildForm
and buildQuery.
bundleForm make sens since this class is based on the AbstractType class from symfony.
But buildQuery is called to construct the query who will bring the result of the filter action on the filter widget.
Then we should conserve the filter class for the widget filter content resolver need who are to display a form.
And create a new type of class filter who are made to talk with widget listing content resolver in order
to filtrate the list.
Resolution Ideas
Dont no yet
Related to
The text was updated successfully, but these errors were encountered: