Skip to content

[Beta] ES6 Section: some missing tests and titles, text needs formatting #12698

@HKuz

Description

@HKuz

Challenge Name

This is a generic issue to help track a few QA tasks for the ES6 section.

Issue Description

The challenges in the ES6 section are all listed below. Each one can benefit from some formatting tweaks in the challenge copy. Also, the challenge titles should follow the [Verb] [Object Clause] format that's used elsewhere (e.g. "Use Conditional Logic with If Statements" or "Comment Your JavaScript Code") and two challenges are missing titles. There are a number of challenges with placeholder tests that need to be written.

  • Explore Problems with the var Keyword
    • Formatting fixes
    • Add test to make sure let keyword is used instead of var
  • Compare Scopes of the var and let Keywords
    • Formatting fixes
    • Temporarily disabled ES6 syntax test
  • Declare a Read-Only Variable with the const Keyword
    • Formatting fixes
    • Write missing tests
  • Mutate an Array Declared with const
    • Formatting fixes
    • Write missing tests
  • Use Arrow Functions to Write Concise Anonymous Functions
    • Formatting fixes
    • Write missing tests
  • Write Arrow Functions with Parameters
    • Formatting fixes
    • Write missing tests
  • Write Higher Order Arrow Functions
    • Formatting fixes
    • Write missing tests
  • Set Default Parameters for Your Functions
    • Formatting fixes
    • Write one missing test
  • Use the Rest Operator with Function Parameters
    • Add title (suggested title: Use the Rest Operator with Function Parameters)
    • Formatting fixes
  • Use the Spread Operator to Evaluate Arrays In-Place
    • Formatting fixes
    • Write missing tests
  • Use Destructuring Assignment to Assign Variables from Objects
    • Add title
    • Formatting fixes
    • Write missing tests
  • Use Destructuring Assignment to Assign Variables from Nested Objects
    • Formatting fixes
    • Write missing tests
  • Use Destructuring Assignment to Assign Variables from Arrays
    • Formatting fixes
    • Write missing tests
  • Use Destructuring Assignment with the Rest Operator to Reassign Array Elements
    • Formatting fixes
    • Write missing tests
  • Use Destructuring Assignment to Pass an Object as a Function's Parameters
    • Formatting fixes
    • Write missing tests
  • Interpolate a String Using Backquotes
    • Formatting fixes
    • Write missing tests
  • Write Concise Object Literal Declarations Using Simple Fields
    • Formatting fixes
    • Write missing tests
  • Write Concise Declarative Functions with ES6
    • Formatting fixes
    • Write missing tests
  • Use class Syntax to Define a Constructor Function
    • Formatting fixes
    • Write missing tests
  • Use getters and setters to Control Access to an Object
    • Formatting fixes
    • Write missing tests
  • Understand the Differences Between import and require
    • Formatting fixes
  • Use export to Reuse a Code Block
    • Formatting fixes
  • Use * to Import Everything from a File
    • Formatting fixes
  • Create an Export Fallback with export default
    • Formatting fixes
  • Importing a Default Export
    • Formatting fixes

Formatting suggestions for the challenge copy:

  • any JS keyword, operator, or method name, etc. should go in code tags. This puts the term in pink-colored text (or green, in night mode). The first instance of a term that is being defined can go in <dfn> tags
  • multi-line code examples should go in blockquote tags, where lines are separated with the br tag. See this example in the code base.
  • Replace the "Instructions" line with a single <hr> tag (the <hr> should be on its own line in the seed file)
  • Notes use <strong>Note</strong><br>Rest of note text... format

One person does not have to do all of these changes. Comment below which challenge(s) you'd like to work on (UPDATE: given some issues writing tests using regex for these challenges noted below it's okay if you just want to work on fixing formatting). Then after the PR is accepted, you can check off what's done. Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedOpen for all. You do not need permission to work on these.scope: curriculumLessons, Challenges, Projects and other Curricular Content in curriculum directory.status: waiting reviewTo be applied to PR's that are ready for QA, especially when additional review is pending.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions