Feature(s) impacted
isFilterable on collection fields doesnt add the filter button if the field type is from type “string”
Observed behavior
Hey,
I have a smart collection which is displayed on via smart relationship in our forest admin.
So far I’ve added isFilterable for fields that are from Enum types with no issue, and off-course the implantation was made in the route file of the parent collection after extracting the filtering params from the actual request ( i.e request.query.filters).
{
field: 'status',
type: 'Enum',
enums: Object.values(StepStatus),
isFilterable: true
},
While adding the isFilterable property to string type field , I could not see the filter icon in the head of the columns
{
field: 'topic',
type: 'String',
isFilterable: true
}
Expected behavior
Filter icon should be displayed in related column, so the param would be extracted in the relationship route.
is there something I am missing in this context?
worth mentioning , the smart relationship route is the one in charge of loading the data.
Context
- Project name: Empathy
- Team name: Empathy
- Environment name: development
- Agent type & version: express
- Recent changes made on your end if any: …