You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
_filter_unused_fields is building list of columns from request, lets assume that there is a field detail.name which is perfectly fine and properly serialized
in the next loop there is a list of keys build in the loop for each record, but this list contains only detail key which is not on the previously built list of columns - in this moment data dissapears from the response... of course, there is an option to keep data despite missing key (datatables_always_serialize list) - but in my opinion for the nested fields default approach should be to keep them without additional hassle
The text was updated successfully, but these errors were encountered:
Hi,
Could you provide sample code so I can reproduce/understand better the issue, also, can you test this issue with version 0.4.0, does it fixes the issue ?
_filter_unused_fields is building list of columns from request, lets assume that there is a field
detail.name
which is perfectly fine and properly serializedin the next loop there is a list of keys build in the loop for each record, but this list contains only
detail
key which is not on the previously built list of columns - in this moment data dissapears from the response... of course, there is an option to keep data despite missing key (datatables_always_serialize
list) - but in my opinion for the nested fields default approach should be to keep them without additional hassleThe text was updated successfully, but these errors were encountered: