This video and the next one can be clearly cut out of this series. They do not bring anything new except for the fact that we do not need commas inside class definitions to separate our method definitions (which could be tacked onto the previous video).
It just seems like an extra that wastes time. Students can clearly go through the code and do the repetitive things on their own. I'd rather see more useful content :-)
Overall, I find this series very useful and easy to follow. Great job!
@Alex - I see your point but disagree.
Having already looked quite a bit into React before following this series, I was surprised the series itself did not started with the ES6 syntax directly, but then I realised that possibly my case (back-end dev recently got more involved in front-end) is not the typical one.
I see that while for me ES6 is just a superior syntax, very similar (or heavily influenced?) by python, for many of my seasoned frond-end colleagues is confusing.
I think the author made a clever decision in starting with ES5 (so that most people will feel "right at home") but then moving to ES6 (if you are picking up React, you are going to write new code, there is no reason whatsoever to use legacy syntax).
Full disclosure: in following the lessons I already used ES6 along the way [and dropped the firething site in favour of redux].
Was puzzled a bit how your app kept working in the first half of the exercise, whilst mine was exploding (due to the lack of "const" keyword in NotesList) - perhaps you had caching / some other confusion your end ? In any case, I spent quite some time debugging before just slogging through the rest of the video with a broken app, and was pleased to see the fix come later on - but some warning to other people "playing along at home" whilst watching might be good, else they end up getting lost down similar rabbit holes.
It's really not, all due respect to Mr Elliott, the es6 class syntax is the least of our problems.
Just in case any beginners read this and get stressed out, I'd like to say I think it's more than fine to use ES6 classes for React. Dan is smarter than I am though and here's his opinion. https://medium.com/@dan_abramov/how-to-use-classes-and-sleep-at-night-9af8de78ccb4#.m2ph4tq8i
The moment I start to refactor NotesList, I start getting the following error:
Warrning: React.createElement: type should not be null, undefined, boolean, or number. It should be a string (for DOM elements) or a ReactClass (for composite components). Check the render method of
Anyone have any idea why this is happening? It triggers as soon as I convert NotesList from `React.createClass` syntax to ES6 class syntax.