HOC: expose wrapped component as WrappedComponent property

[naholyr]

Hi, this PR will add a public static property WrappedComponent (tests included) to access original component.

It looks like a de facto standard in higher order components, at least that's what react-router and react-redux do, so I expected any higher order component to do the same. This allows to access original component in a standardized way and access its original static properties (in my case, a loadData property used for server-side data fetching, but that could be anything else). Without this property, I can't use your HOC with mine as it "breaks the chain". This PR includes implementation and test 👍

Thanks for your work!

Note: this is quite the same PR which was merged last week in dunglas/react-esi#6

[coveralls]

Coverage increased (+0.07%) to 91.915% when pulling 64a5ded on naholyr:feat/expose-wrapped-component into 58d508b on i18next:master.

[jamuhl]

For consistency in the code - can you do the same for: https://github.com/i18next/react-i18next/blob/master/src/withSSR.js

[naholyr]

Obviously, I'll do it tomorrow ;) I did not give attention to this one as he's not as used, but you're right. Le sam. 18 mai 2019 à 14:30, Jan Mühlemann <[email protected]> a écrit :

…

For consistency in the code - can you do the same for: https://github.com/i18next/react-i18next/blob/master/src/withSSR.js — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#853?email_source=notifications&email_token=AABUIM3STJV7JLQ6HW2KASDPV7ZEZA5CNFSM4HNU7LJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVWNZIA#issuecomment-493673632>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABUIM4HOYYSJBHDAQUHFYLPV7ZEZANCNFSM4HNU7LJQ> .

[naholyr]

PR updated with withSSR (force-push to keep it single-commit)

[jamuhl]

thank you...was published in [email protected]