-
-
Notifications
You must be signed in to change notification settings - Fork 638
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
I18n::ArgumentError with i18n v0.8.2+ #415
Comments
I have just released I18n 0.8.4 which should fix this issue. Please try it out :) |
This might be just my opinion but I think it's more CanCanCan's fault than i18n's: A call to |
I agree with @clemens , PR is welcome! |
is the problem with i18n solved now @cbeer ? |
I guess it is solved by the i18n update but (IMO) it's not fixed in the right way ... |
Steps to reproduce
https://gist.github.com/cbeer/140cb717506e97181644c59faaef92b2
Using i18n v0.8.2+, calling
unauthorized_message
causes an exception.Upstream, they introduced a new check in 0.8.2: ruby-i18n/i18n#236.
Cancancan is explicitly passing a
nil
key:cancancan/lib/cancan/ability.rb
Line 225 in 2d21842
Expected behavior
The unauthorized message should be provided.
Actual behavior
An exception is thrown:
System configuration
Rails version: 5.0.2
Ruby version: 2.3.4
CanCanCan version 1.17.0
The text was updated successfully, but these errors were encountered: