Multi Select cannot filter

[suwubee]

I create MultiSelect, but cannot filter it.

[greptile-apps]

Disclaimer: This comment was automatically generated with AI. It can give some useful hints as to where to look for, but sometimes it can also give very inaccurate answers so takes this with a pinch of salt :).
To address the issue of the MultiSelect component not filtering options, ensure the searchFilter state in MultiSelectFieldInput.tsx is correctly applied to filter optionsInDropDown. Currently, optionsInDropDown does not utilize searchFilter for filtering options. Implement filtering logic similar to: javascript optionsInDropDown.filter(option => option.label.toLowerCase().includes(searchFilter.toLowerCase())) Also, verify that useFilterDropdown and useMultiSelectField hooks properly manage state changes related to filtering. This might involve ensuring that the component re-renders upon searchFilter state changes and that the filtering logic is correctly applied within these hooks.

References

/packages/twenty-front/src/modules/object-record/object-filter-dropdown/components/ObjectFilterDropdownOptionSelect.tsx
/packages/twenty-front/src/modules/object-record/record-field/meta-types/input/components/MultiSelectFieldInput.tsx
/packages/twenty-front/src/modules/object-record/object-filter-dropdown/hooks/useFilterDropdown.ts
/packages/twenty-front/src/modules/object-record/record-field/meta-types/hooks/useMultiSelectField.ts

Ask Greptile

[rob-luke]

I confirm I have the same bug on v0.11.3 and v0.12.1

[FerdiHr]

Same here

[gitstart-app]

Here is the GitStart Ticket for this issue: https://clients.gitstart.com/twenty/5449/tickets/TWNTY-5358

[FelixMalfait]

Thanks for the report!

@gitstart-twenty could you please take care of this? And do a quick audit of any other missing filters for various field type? (we don't want to be exhaustive as some don't make much business sense but we might have missed important ones like the one above ; see also #5216 which is ongoing)

[charlesBochet]

@FelixMalfait pg_graphql does not support filtering by Array at the moment. This ticket cannot be done until we migrate out of pg_graphql or they update their filtering feature

[FelixMalfait]

@charlesBochet seems like this was just implemented! supabase/pg_graphql#520

[FelixMalfait]

Released yesterday: https://github.com/supabase/pg_graphql/releases/tag/v1.5.6

[martmull]

@FelixMalfait @charlesBochet @suwubee, well, think we have to wait a little bit to have enum filter support -> supabase/pg_graphql#530

[rob-luke]

Excited to see that this issue moved to done in the product development project 🚀 . Is this issue now closed? I am very excited to use this 😄 @martmull @charlesBochet

[FelixMalfait]

Unfortunately this is still stuck due to the issue linked above by @martmull - we cannot solve this as long as the above issue isn't solved

[john-ramsey]

Potentially tangental comment but worth calling out that pg_graphql isn't supported as an extention in GCP CloudSQL, Azure Database for PostgreSQL or AWS RDS.

While likely a large item to migrate away from pg_graphql this should be added to the list of reasons.

[FelixMalfait]

@john-ramsey Yes the pg_graphql did an amazing job that allowed us to move faster initially, but long-term we'll probably have to replace because of the limitations (another one is the inability to filter by a nested object's property)

[rob-luke]

In case its useful for anyone else. I have temporarily got around this by writing a script that copies the multi select fields as text in to a text field called "multiselecthack", and then I can filter based on that. But this quickly causes you to hit this issue: #5056

[charlesBochet]

This will be possible as we move out of pg_graphql

[Sytten]

I would also suggest not using postgres enums as they are very limiting (you can't remove options, reorder, etc). In general it is easier to use a check constraint or verify in software (and use plain strings in db).

[charlesBochet]

@Sytten we actually already support postgres enum editing (we have some code handling it and agree it was not a piece of cake!) as data integrity is quite important for Twenty

This ticket is unblocked now :)