-
Notifications
You must be signed in to change notification settings - Fork 21.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
helper :all from ActionMailer #1582
Comments
@marcandre Not sure if this is still a issue. can you please confirm??? |
Closing this. Please feel free to reopen it again if issue still exists for you. Thanks! |
This is still an issue: my_mailer.rb my_mailer_spec.rb end ↪ rspec ./spec/mailers/my_mailer_spec.rb as well as: /Users//.rvm/gems/ruby-1.9.3-p194-perf@www/gems/activesupport-3.2.9/lib/active_support/dependencies.rb:317:in `rescue in depend_on': Missing helper file helpers/all_helper.rb FWIW, here are the rest of the gory details: |
👍 this is a confusing difference. |
@rafaelfranca thanks for re-opening. It looks like #928 is the same issue, imported from Lighthouse and @neerajdotname had a fix mentioned in the comments at https://github.com/neerajdotname/rails/commits/fix_for_6575, but that link is now 404ing. Maybe he can resurrect that branch? |
@phillbaker I remember having worked on it. I don't have that fix locally too. I'll work on it. |
I honestly can't see the appeal on including |
The documentation for
AbstractController::Helpers#helper
states that:all
is a special parameter.Indeed, from a
ActionController::Base
,helper :all
will use all the helper files. It even does that by default in Rails 3 / 3.1rc1.On the other hand, this doesn't work from
ActionMailer::Base
and we get:Note that
ActionMailer::Base < AbstractController::Helpers
is true.It would be nice if
helper :all
could work forActionMailer::Base
also.If it did, maybe
ActionMailer::Base
should call it by default, asActionController
doesIf it wont, and
:all
can not handled by all descendants ofAbstractController::Helpers
, then the doc should be updated to reflect this.Comments to be found in the imported issue
The text was updated successfully, but these errors were encountered: