[Nitro] Og conflicts with Narf (Mechanize)
rob at motionpath.com
Wed Feb 15 10:18:52 EST 2006
I've mentioned this before (polluting the global namespace) and even
provided a patch to remove Glue from the global namespace. I agree it's
a bad idea, but George really likes it and my final position is it
should be an option (enabled by default, but you may disable, which my
patch provided for and has been running here in production with no
issues so far).
On Wed, 2006-02-15 at 15:08 +0100, Kashia Buch wrote:
> Tag vs Tag
> in Narf: web/tagparser.rb
> So you can't run Mechanize/Narf with a Nitro/Og application with an "is Taggable" class.
> I ran into Zimba on the IRC channel and he did a quick fix for me, he just moved the Tag class into the Glue namespace.
> This now prevents those two from clashing, but I'm not entirely convinced that this is the correct way, since this changes the database table name from ogtag to ogglue_tag.
> I don't know how many applications that would break (although it can be fixed easily)
> [14:55] <zimba-tm> also, for your table problem, you should be able to set it by hand.
> [14:56] <zimba-tm> you just have to reopen the Glue::Tag class and set the table_name
> what do you think about the issue?
> Zimba pointed out that it's not good idea to pollute the global namespace, which I agree to.
More information about the Nitro-general