-
Notifications
You must be signed in to change notification settings - Fork 24
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
render 'Contain' with null #58
Comments
I think the only solution to this problem is to use a custom render callback which can then ignore null objects. |
I agree it has been a very annoying. But the only solution I know is to use a customer render. |
Right now we use I wonder if we should use a default render callback that also ignores NULL. So far I found it might be better to not silently fail by default. But I wonder if we should have a 'defaultRenderCallback' kind of config for the helper. |
I honestly think just using a custom rendered is fine. Im my use cases mainly I'm generating a link to a belongsTo relationship anyways so during the link generation I'm checking for null. |
below this is main query with null return, render with 'number' parameter without problem.
number":null,"user":{"username":"test"}
below this is contain query with null, since render parameter is 'user.username', so datatable cant get '.username' and popup an error.
number":null,"user":{"user":null}
any solutions? thanks
The text was updated successfully, but these errors were encountered: