Implement filter on composite sub fields that contain arrays #7188
Assignees
Labels
Comments
This was referenced Sep 20, 2024
lucasbordeau
added a commit
that referenced
this issue
Oct 8, 2024
# This PR - Fix #6425 See #7188 because there's some more work to do. --------- Co-authored-by: Lucas Bordeau <[email protected]>
harshit078
pushed a commit
to harshit078/twenty
that referenced
this issue
Oct 14, 2024
# This PR - Fix twentyhq#6425 See twentyhq#7188 because there's some more work to do. --------- Co-authored-by: Lucas Bordeau <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scope & Context
Follow-up of #6425
We implemented filtering on composite field types like ADDRESS and LINKS.
The problem is that we still have to implement filtering on their subfields like
secondaryLinksoradditionalPhonesbecause they need a special treatment, they are like sub-sub-fields.Current behavior
Currently we can filter on sub field of level 1.
Expected behavior
We want to be able to filter on sub fields that contains arrays, sometimes arrays of objects like
additionalPhoneswhich contains an array of PhoneRecord :additionalPhones?: PhoneRecord[] | null;Technical inputs
See if there's some work on the backend involved ?
We'll also have to handle the filtering for the frontend cache that mirrors the backend filtering for those fields.
The text was updated successfully, but these errors were encountered: