-
Notifications
You must be signed in to change notification settings - Fork 42
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
do not pass i13n props to string components #96
Conversation
CLA is valid! |
👍 thanks @sebastiendavid for fixing this, overall the strategy is good, not sure why build failed, will check and get this merge soon |
Yes I don't understand which step is failing during the tests. For me |
👍 |
I just check out the repo and ran it locally by I can see this test error
could you check? @sebastiendavid I'm thinking that might be |
Ah yes of course, I did not change my node version, I was using node v4. I will make it compatible for node v0.12 tomorrow, it's late here ;) |
thank you @sebastiendavid , but we will still running it on 0.12 since it's still being used |
|
@sebastiendavid there's a node version update on master, could you just |
e4e6fd3
to
ab90092
Compare
done |
it's published, thanks @sebastiendavid https://github.com/yahoo/react-i13n/releases/tag/v2.1.2 |
Thanks :) |
To avoid to pass i13n props to string components such
a
orbutton
, we can filter the props before passing them to the wrapped component. So React ^15.2.0 will not warn about unknown props. What do you think?