Create instance own localize method #209
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Each instance of the
Localize
class should have its own (as inhasOwn
)localize
method to store its resources and other localization-related state.This is not applied to the
LocalizeClass
so that other uses, like for component mixins, can continue to share resources per-component. There is some light additional work to be done incore
to fully take advantage of this because it's currently re-fetching for each element even if the component has its resources. However, that can be done separately from this change.Using
getPrototypeOf
/super
instead ofbind
has the advantage of keeping the sharedlocalize
method and not hogging memory, with no hit to speed.