Change:
The description of the project to build football team cards in the js beta curriculum says: In this project, you will build a set of football team cards and learn about nested objects, object destructuring, default parameters, event listeners, and switch statements. But switch statements were introduced in the date formatter project (step 16, 17). I think the description should be modified therefore to not mention learning switch statements. I haven't actually done this project, so I don't actually know if it re-teaches switch statements or not. (it would be nice if the date formatter description mentioned learning about switch statements though) N/A N/A No response N/A No response
I don't really get the title of this challenge, what "modern javascript methods" is it referring to, is it just the ? Because surely both map and filter has already been taught at this point. I'm also not sure the switch is really needed. It seems a little verbose and a lot of boilerplate. Compared to say:
Let's go ahead and remove switch statements from the description and the first step.
I feel like the switch used in the code is because the idea of the challenge, among other things, was to teach it. It takes up a lot of the total code. Not mentioning it, doesn't really change that fact. Not unless, we remove the switch from the code as well.
That's a fair point. I'd be fine rewriting the challenge to use the example you shared earlier.
Hi! I am a new, first time contributor. Can I put up a PR for this issue? Seems like a simple fix, just removing 'switch statements' from description and first step
It could be seen as reinforcement. I'm not saying we have to remove it, I'm just saying it seems like part of the point of this challenge was to teach the switch, which is why it is in the description and the code. Not sure how often we use switch statements, but this project is definitely reinforcing it. So we might want to keep it just for that reason. This also isn't the first time we teach and it is in the description as well. Maybe that could be it, reinforcement. Or something like that?
changing the description slightly seems like an easy way to fix the issue
I like this copy, yeah.

Discussion:
"title": "Learn Modern JavaScript Methods by Building Football Team Cards", "intro": [ "One common aspect of building web applications: processing datasets, and then outputting information to the screen. In this sports team cards project, you'll learn how to work with DOM manipulation, object destructuring, event handling, and data filtering.", <del> "This project will cover concepts like switch statements, default parameters, <code>Object.freeze()</code>, the <code>map()</code> method, and more." </del> <ins> "This project will cover concepts like, default parameters, <code>Object.freeze()</code>, and reinforce your knowledge of the <code>switch</code> statement and <code>map()</code> method." </ins> ] }, "learn-advanced-array-methods-by-building-a-statistics-calculator": {

# --description-- <del> In this project, you will build a set of football team cards and learn about nested objects, object destructuring, default parameters, event listeners, and switch statements. All of the HTML and CSS for this project has been provided for you. </del> <ins> In this project, you will build a set of football team cards and learn about nested objects, object destructuring, and default parameters. All of the HTML and CSS for this project has been provided for you. </ins> Start by accessing the `id` called `"team"` from the HTML document and storing it in a `const` variable called `teamName`.