Quotes & Key Ideas:
- “Template literals allow you to create multi-line strings and to use string interpolation features to create strings.” The are created using the following syntax:
variableis your desired output.
- ES5 uses the keyword
functionwhile in ES6, you can remove the
functionkeyword and colon altogether when defining functions in objects.
- “ES6 provides a new syntax to create objects, using the class keyword. It should be noted that the class syntax is just syntax, and not a full-fledged class-based implementation of an object-oriented paradigm, unlike in languages such as Java, Python, Ruby, etc.”
- “UpperCamelCase should be used by convention for ES6 class names”
- “It is convention to precede the name of a private variable with an underscore (
_). However, the practice itself does not make a variable private."
A different syntax is used for importing default files:
“To import a default export, you need to use a different import syntax. In the following example, add is the default export of the
math_functions.js file. Here is how to import it:
import add from "./math_functions.js";
The syntax differs in one key place. The imported value,
add, is not surrounded by curly braces (
add here is simply a variable name for whatever the default export of the
math_functions.js file is. You can use any name here when importing a default."
I feel a lot of ES6 challenges are taken out of context, I’m hoping they’ll make more sense as I progress and see how their used in practice. If not, then I’ll need to study them in more detail. The template literals and regex (so far) were pretty straight forward to me — I’ve played around with regexes before in a Python course. Some of the shorthand syntax is a little weird and I’m struggling to wrap my mind around it, but I think with practice it’ll sink in better.
For music today, I went back to the Battlestar Galactic song Prelude to War (on repeat to keep me focused).
Overall, I’m very satisfied with the progress I made today (especially since I completed a section of the course) and I’m looking forward to the next. I’ve still got 7 more sections to go until I get to the projects which are always ‘fun’ challenges because that’s when you get to put it all together.
Link to work:
For my progress visit the timeline on my freeCodeCamp Profile.
My full log for the #100DaysOfCode challenge can viewed on GitHub.