3 ms·
I've been writing Ruby professionally for six years and this has never been an issue for me or folks I work with. Can you give a single example where you found
by kaiuhl 14y ago
I've been writing Ruby professionally for six years and this has never been an issue for me or folks I work with. Can you give a single example where you found a conflict in libraries that broke your application?
- mjw 14y agoI ran into a nasty bug a while back which came down to a conflict between two JSON libraries in their definitions of #to_json on core classes.
- aneth4 14y agoI have seen issues quite a few times, and they are serious headaches to fix when they come about. I've had libraries implement Rails utility methods slightly differently, or conflicting implementations of monkeypatches on S3 libraries. While it's not incredibly common, disrespecting namespace concerns is a sure road to problems.
- jamie_ca 14y agoRake::RemoteTask (a dependency of Vlad) defines a bunch of stuff on Kernel, including #role. For whatever reason, if an ActiveRecord model includes role as a property, things break in weird ways. Reasonably easy to work around by aliasing/undefing Kernel#role to #server_role or something, but amusingly that would be something that could be fixed by refinements (though I'd rather see something more like Thor, that's not run toplevel).