-
Notifications
You must be signed in to change notification settings - Fork 899
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
wrong number of arguments on add_flash_types for version 5.0.0 #791
Comments
Does |
Yeah, it does. So, I don't recommend using the name "warn" for a flash type. In my mind, it's as if you defined a new method named "puts", and then were surprised when That said, PT could use an explicit receiver, e.g. |
Some people override warn in their applications. Using an explicit receiver protects against this. [Fixes #791]
Some people override warn in their applications. Using an explicit receiver protects against this. [Fixes #791]
Closed by #793, but please reconsider overriding the |
👍 |
@jaredbeck I'm surprised that Rails 4 creates a method via add_flash_types, I did not know that. Thanks for the tip and the quickly fix. (: |
Rails loves to create methods at runtime :) When you call
http://guides.rubyonrails.org/association_basics.html#has-many-association-reference |
Some people override warn in their applications. Using an explicit receiver protects against this. [Fixes paper-trail-gem#791]
Updating from paper_trail
4.1.0
to5.0.0
, it raises error on my flash register:If I comment it, the error goes way. Currently I'm not using the paper trail, I just have it on my Gemfile.
The text was updated successfully, but these errors were encountered: