-
Notifications
You must be signed in to change notification settings - Fork 229
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
react 14 and 15 testing identified warning in react 15 #183
Conversation
we need to move away from using defaultValue as its now a react thing and not just a react-typeahead thing. defaultValue is for uncontrolled components we can use value. http://facebook.github.io/react/docs/forms.html#controlled-components |
…r public facing api. defaultValue is for uncontrolled
I've bumped to 2.0.0 to move from using defaultValue to using initial value, tests passing. |
testing scripts inspired by airbnb's enzyme testing library. https://github.com/airbnb/enzyme/blob/master/package.json |
anyone waiting on this theres a public fork on @pebblecode/react-typeahead |
@export-mike - any preference on going straight to 2.0.0 vs doing a 2.0.0-rc.1? |
@fmoo This dropped off my radar. I had made some v2 changes and was in the process of setting up React Storybook to try and get some use cases documented. I've done a hasty patch to try and get rid of that aspect, and there's a big https://github.com/fmoo/react-typeahead/compare/master...nosilleg:v2?expand=1 Another change would have been to remove |
I suck at npm, but this seems fishy: with the react 15 peerDep bump, should we bump react-dom and react-addons-test-utils as well?
|
Released as [email protected] |
We shouldnt need to bump peer dependencies, within this branch I've added npm i [email protected] and npm i react@15 as part of test scripts, this way we can support both. @fmoo what version of npm are you on? |
Just a thought let's update the npm test script to call npm run test:all? |
Cool I can test this out in a few hours I'm using my phone atm |
I installed react 15.0.1 globally |
If you remove react from global dependencies and use the new On Thu, 21 Apr 2016 06:04 Peter Ruibal, [email protected] wrote:
|
I have identified warnings regarding the new warning added in react 15,
as discussed on react blog and github PR
https://facebook.github.io/react/blog/2016/04/07/react-v15.html#new-deprecations-introduced-with-a-warning
facebook/react#5048
This PR contains how to identify the problem:
new run script:
npm run test:react:15
npm run test:react:14
I will submit a following PR to show how this will be fixed.