Added WrappedComponent property to translate wrapper #15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
import { translate } from 'react-i18next/lib';
export default function translateMixin(translations) {
return (WrappedComponent) => {
const componentFunc = translate(translations)(WrappedComponent);
componentFunc['WrappedComponent'] = WrappedComponent;
return componentFunc;
}
}This is what I have to do as a workaround |
jamuhl
added a commit
that referenced
this pull request
Feb 24, 2016
Added WrappedComponent property to translate wrapper
|
just published v1.1.0 |
|
thank you for the contribution |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When you wrap component in translate, you loose any reference to it.
This is for example required when you're doing server-side rendering, and Component defines which actions to do to prefetch data.
Same approach is used in react-redux connect wrapper