https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33873
--- Comment #16 from Martin Renvoize <[email protected]> --- Hmm.. I think we still need this though.. I fixed a very similar issue recently in 744ac4825ba9a346e2ad1c8e413d3d9423658512 (Bug 33504: Update patron_to_html to deal with null) In the above commit I wrote: > In the patron_to_html function we were dealing explicitly with the case > where patron may be passed undefined, but forgetting that it may be > returned as 'null' from the api too. Changing from `( patron === > undefined )` to `( patron == null )` is the recommended approach for > detecting 'undefined or null' in javascript. Do we have a preference for `!biblio` vs `biblio == null`.. They are equivalent right? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
