At the end of the post, the author says: "this issue wont be fixed for now." I asked on Twitter for more details, and this was his reply:
> response was roughly like "We might change this in Rails 4" and "$affected_lib should fix it on its side"[1]
> response was roughly like "We might change this in Rails 4" and "$affected_lib should fix it on its side"[1]
No comments yet.