`const location` is once again breaking everything~ · Issue #66952 · freeCodeCamp/freeCodeCamp · GitHub
Skip to content

const location is once again breaking everything~ #66952

@naomi-freecodecamp

Description

@naomi-freecodecamp

Okie dokie, sooooooooo~

We get a lot of campers who end up writing const location in their JavaScript code and Babel loves to turn that into var location and that overwrites the global location and everything goes all oopsie whoopsie~

So Naomi has a plan! We're gonna do some clean-up in the curriculum and resolve some of this confusion!

Here's what we gotta do:

🔴 These workshop(s) actively use const location in the JavaScript seed or instructions. As such, they have a CURRENT AND IMMEDIATE risk of global variable conflict~

  • workshop-heritage-library-catalog

🟡 These workshop(s) have an HTML element that has id="location" in the seed or instructions, AND include steps that use JavaScript. As such, they have a significant risk of global variable conflict~

  • lab-weather-app
  • workshop-hotel-feedback-form

And a pretty task list:

  • Heritage Library Workshop
  • Weather App Lab
  • Hotel Feedback Form Workshop

Here's the dealio~ Naomi gotta touch base with a couple of colleagues first, but I will be opening this up as part of Naomi's Sprints This label is for issues that Naomi is managing through her sprint initiatives on Discord. so if you would like to take on one of these make sure you are in our Discord community and have self-selected the Naomi's Sprints role~

Metadata

Metadata

Assignees

No one assigned

    Labels

    js v9 certThis is for the JS V9 certification.status: discussingUnder discussion threads. Closed as stale after 60 days of inactivity.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions