React v15.5.0
facebook.github.io
React v15.5.0
1–10 of 209 posts
Re: React v15.5.0
#2Big news seems to be removal of `React.createClass()` in favor of:
class HelloWorld extends React.Component {
}Re: React v15.5.0
#3Fiber is what I'm really waiting for. Not much official chatter about it, but looks like a 16 release?
They just removed some addons in master that many third party packages rely on, including material-ui. Hopefully these other popular packages can be ready to go with the changes when the fiber release hits.
Re: React v15.5.0
#4For those still using propTypes, I'd recommend to take a look at Flow as replacement.
Re: React v15.5.0
#5Fiber is what I'm really waiting for. Not much official chatter about it, but looks like a 16 release? They just removed some addons in master that many third party packages rely on, including material-ui. Hopefully these other popular packages can be ready to go with the changes when the fiber release hits.
This is the prep for fiber. They're releasing something with deprecation warnings so when they have to completely remove those things in 16 (w/ fiber), everyone will be ready.
Re: React v15.5.0
#6Big news seems to be removal of `React.createClass()` in favor of: class HelloWorld extends React.Component { }
Uh, so they take the step to 100% ES2015, yes?
Re: React v15.5.0
#7I still remember the times when warning were actual likely mistakes in your code, not "we're adding some more churn, update your stuff until we churn more".
If you want people to always ignore warnings, this is how you go about it.
Re: React v15.5.0
#8I still remember the times when warning were actual likely mistakes in your code, not "we're adding some more churn, update your stuff until we churn more". If you want people to always ignore warnings, this is how you go about it.
Baloney. This is proper release management planning. People keep complaining that React is too big and needs to shrink down. They're planning to help address those complaints by removing pieces they no longer intend to maintain, or are not the primary usage going forward. So, they're putting out a minor release that will warn people these pieces are being removed, and then they'll be removed in the upcoming major release. Seems like the right approach to me.
Re: React v15.5.0
#9I still remember the times when warning were actual likely mistakes in your code, not "we're adding some more churn, update your stuff until we churn more". If you want people to always ignore warnings, this is how you go about it.
If you don't want to upgrade to React v16, why would you upgrade to React 15.5.0 (which includes the new warnings)?
Re: React v15.5.0
#10Of course, you'd need to use super appropriately, but I wonder if anyone's taken a stab at porting React mixins to ES2105 mixins:
http://justinfagnani.com/2015/12/21/real-mixins-with-javascr...