-
Notifications
You must be signed in to change notification settings - Fork 148
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
Memoization stopped working on upgrading to 1.0.0 #128
Comments
Thanks for reporting the issue. I'd go with the first solution and update the README. |
Hey @timfjord We have raised a PR for the first solution here #129 On skimming through code from other i18n backends(simple, key-value), we noticed that the they all have Implementation module present. And they follow the convention of Should we also be in sync with other I18n backends and use Implementation module? |
Hey @abime Thanks for sending the PR Yeah, I've been thinking about this and I think are right, it is better to stick to the convention and bring the |
@timfjord We've made the necessary changes and rebased the branch with master. Please re-review. |
Awesome, thanks @prayeshshah |
Just released v1.1.0 Thanks for the contribution @prayeshshah and @abime |
We found that Memoization stopped working on upgrading to 1.0.0.
We believe that the issue got introduced in this #124, where Implementation module got removed and it affected the ancestor chain.
Initially lookup method from Memoize module used to take the precedence but after removal of Implementation module
lookup
method ofI18n::Backend::ActiveRecord
is called.Ancestor Chain in 0.4.1
Ancestor Chain in 1.0.0
Two possible solutions to make memoization work
prepend
instead ofinclude
in the initializer. If we consider taking this approach, we need to make changes to the readme and the initializer generator code.Implementation Module
.Let us know what you think and we can raise the PR accordingly.
Co-Authored by @prayeshshah
The text was updated successfully, but these errors were encountered: