Re:The Great CoffeeScript to Typescript Migration of 2017
by dgoldstein0 on Saturday May 16, 2020 @09:34PM
(#23208703)
Another bad one: returning a jQuery.ajax object, and then consumers of your api may start using it directly.
We have that in our codebase still. Not sure if it was intentional or not but it's going to be hard to undo.
My favourite implicit return gotcha comes from the intersection of CoffeeScript and jQuery, where implicitly returning `false` from an event handler implies `preventDefault()` and `stopPropagation()`. This can even cause heisenbugs if your logging throws booleans around.