-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to search null field on search resources / improve parse query on null handling #2177
Conversation
module: `${testModuleRealm}friend`, | ||
name: 'Friend', | ||
}, | ||
every: [{ eq: { firstName: 'Mango' } }, { eq: { friend: null } }], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what i test in the CRM app, both { eq: { assignee : null}}
or { eq: { 'assignee.id' : null}}
able to give the same expected result after the fix
4c2b10a
to
79fa53e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
( NOTE: found this is not valid after fix the first issue and did several tests locally )
Good find on this!
We have a scenario to get CRM task cards with no assignee when user clicks 'Unassigned' filter
Two layer of issues found with @tintinthong
null
value on query, it parses as empty string - so search doc couldn't find any cards of field which hasnull
valueassignee: null
as it gives error about compound field ( NOTE: found this is not valid after fix the first issue and did several tests locally )Solution
strictNullHandling
Examples
Search doc of CRM task card with no assignee

Error when filtering assignee null before the fix


After fix
