You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the :en locale is not included in an application's locales, which is my case, an I18n::InvalidLocale exception will be raised within the rescue block, effectively blocking the developer from gaining insight into what actual exception has occured.
But it's rather specific to my use case and far from perfect for general usage. However, the current implementation is also not perfect in the edge case of apps that do not have a :en locale.
The text was updated successfully, but these errors were encountered:
kryzhovnik
added a commit
to kryzhovnik/carrierwave
that referenced
this issue
Dec 16, 2016
…gick#manipulate!
Since ([commit on May 9, 2014](ruby-i18n/i18n@b5703d7)) enforce_available_locales in I18n is true by default, the aproach which implies on default error messages from `:en` locale is broked for all apps where `:en` is not available locale.
If a MiniMagick::Error or a MiniMagick::Invalid exception is raised within
manipulate!
, the rescue block will try to find a default error message withIf the :en locale is not included in an application's locales, which is my case, an I18n::InvalidLocale exception will be raised within the rescue block, effectively blocking the developer from gaining insight into what actual exception has occured.
I'm currently using this as a workaround:
But it's rather specific to my use case and far from perfect for general usage. However, the current implementation is also not perfect in the edge case of apps that do not have a :en locale.
The text was updated successfully, but these errors were encountered: