Rails - Feb 2005 - Modules Beta Comments

I''m not sure but I think this is due to the ''modules''
support in the
latest beta gems.

In some controllers I include small utility classes that only make 
sense for that controller. Something like this:

  class SantasLittleHelper < Foo
  end

  class FooController < ApplicationController
  end

Where Foo is defined in RAILS_ROOT/lib/foo.rb

What I am seeing now with this new beta is this:

  #<NameError: uninitialized constant Controllers::SantasLittleHelper>

The ''Controllers::'' part makes me think this has something to
do with
the new modules support.

Help :-)

  S.

On Feb 15, 2005, at 8:29 PM, Stefan Arentz wrote:
> I''m not sure but I think this is due to the
''modules'' support in the
> latest beta gems.
>
> In some controllers I include small utility classes that only make 
> sense for that controller. Something like this:
>
>  class SantasLittleHelper < Foo
>  end
>
>  class FooController < ApplicationController
>  end
>
> Where Foo is defined in RAILS_ROOT/lib/foo.rb
>
> What I am seeing now with this new beta is this:
>
>  #<NameError: uninitialized constant Controllers::SantasLittleHelper>
>
> The ''Controllers::'' part makes me think this has
something to do with
> the new modules support.
Ahhh. In my case this was a simple matter of a

  require ''foo''

which of course makes sense; the default namespace has changed.

This is a gotcha that should be noted somewhere :-)

  S.