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
Description
Many of the available Filters in api-platform/core seem to not be properly supported by the PWA.
In my example, the following SearchFilter and OrderFilter attributes with nested properties are configured for the Coffee entity:
The backend part works as expected, so I can order and search by the given nested properties on the API itself. Also when I manually edit the respective query params in the HydraAdmin URL, it properly shows the searched and ordered results.
Here using beans.type=/bean_types/{id}
And here using beans.type.name={name}
The actual problem seems to be in the HydraAdmin so that it does not offer the nested properties in the "Add Filter" section and also it does not show it under "Active Filters".
A similar but a bit different problem happens for the OrderFilter with nested properties: When I manually set it in the query params it works, but when clicking on the roaster-order it sends order=roaster instead of order=roaster.name
Another broken case is the RangeFilter.
It passes the filter properly to the API but does not show it under add filters or active filters.
Activity
slax57 commentedon Jun 13, 2025
Reproduced, thanks!
There are evidences in the code suggesting this is supposed to work (or at least did at some point) so I'm marking this as a bug.
admin/src/introspection/schemaAnalyzer.ts
Lines 33 to 46 in 2027186
Thanks for the report.