Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialColin Sandlin
4,512 PointsCan you please redo this entire section without using callback/arrow functions?
Not necessary and makes it 1000x more confusing for people just jumping into the JS world.
Eric Butler
33,512 PointsArrow syntax can get more complex/different looking, like when you start adding arguments and removing parentheses and curly braces, but this example/lesson is the simplest it gets so that's all the difference there is.
1 Answer
Eric Butler
33,512 PointsFYI, addEventListener requires a callback function to work, so that has to stay. But you have a point, you could write the function in traditional JS instead of the new arrow function syntax. Just real quick so you can keep progressing, here's what that would look like:
listItems[i].addEventListener('mouseover', function() {
listItems[i].textContent = listItems[i].textContent.toUpperCase(); // this would be the exact same
});
You'd literally just be changing () =>
to function()
. And while I dislike the new arrow syntax too and think it's harder to understand, it's better that you're learning that first because honestly, it's not going back to the old way, ever. JS is moving rocket-speed toward this new syntax.
Colin Sandlin
4,512 PointsColin Sandlin
4,512 PointsCool, thanks Eric. That was helpful. For some reason I thought arrow syntax was more complex than just replacing the "function()" item.