https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37492 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |36196 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36196 [Bug 36196] Handling NULL data in ajax calls for cities -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37492 Victor Grousset/tuxayo <victor@tuxayo.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |victor@tuxayo.net --- Comment #1 from Victor Grousset/tuxayo <victor@tuxayo.net> --- (In reply to Victor Grousset/tuxayo from bug 36169 comment #4)

This seem to be the proper way to handle null values: https://stackoverflow.com/questions/48917064/how-do-you-properly-handle-null... values-in-datatables/48920248#48920248 Hopefully that works in our case.

From reading quickly: Adding «"defaultContent": ""» And maybe having to change our "targets" value if for some reason it only work with '_all' (and that we somehow can get away without [0,1,2,3,4])

(In reply to Victor Grousset/tuxayo from bug 36169 comment #5)

Another source: https://stackoverflow.com/questions/57711349/how-to-deal-with-null-values-in... jquery-datatable-when-using-ajax/57714479#57714479

---

And another. According to the usage of defaultContent there, we can even target individual columns for default values: https://datatables.net/forums/discussion/50823/handling-null-values

So it seems pretty sure we can use that.

-- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.