Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Happy days, yesterday we updated form 16.3 to 16.4 and thanks to them fixing the bug in 'getDerivedStateFromProps' my broken code is now breaking.
Don't you just love it when features inadvertently depend on bugs. The entire component ONLY worked properly because of a react bug.3 -
Hi there!
What do you guys think about the feature "ContextApi" released with React 16.3?
From my point of view it is pretty neato to get rid of some dependencies coming up with redux, if the only thing you want is to distribute collected information among several components for rendering.
On the other hand, if one replaces the redux pattern with the context-api, the detailed information for debugging will be lost, including the time-travelling feature.
For compensation, there is a guy who had built a bridge between the context-api and the redux dev tools, which even will restore the ability to time-travel through the information flowing through the react context.
https://medium.freecodecamp.org/rep...
I will definitely try out a migration of our redux structure to context-api in an experimental branch of one of our products! -
Some of my first thoughts on the new 16.3 release of React...
New Context API:
- I’m glad they made the context API less scary, but as a redux user I will still be staying away from using context as a best practise.
Strict Mode:
- I like this a lot. React allows for great freedom in how you do things, but also offers the freedom to write some shit code that in the end does the job. A way to enforce best practises in JSX is good in my eyes.
New lifecycle methods:
- meh. Life moves on
https://medium.com/@baphemot/...
Top Tags
Weekly Rant
View