javascript-tutorial / javascript-tutorial/en.javascript.info

Debug code does not match lesson

Open
#3,729 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
25.5k
Forks
4k
PR merge metrics
No merged PRs in 30d

Description

Code Quality - 1. Debugging in the Browser, example page

The code shown in the sources panel is currently condensed to only two lines:

function hello(name){let phrase=`Hello, ${name}!`;say(phrase);}
function say(phrase){alert(`** ${phrase} **`);}

This is rather than spread over nine lines as shown in both the examples and repo .

Editing the source in browser does allow for the addition of breakpoints but upon directed refresh the code is reset to its original state and the results do not match those in the tutorial text.

Given the repo code seems to be as intended suggests perhaps a deployment issue.

Confirmed with browser versions:

  • Chrome: 126.0.6478.185 (Official Build) (64-bit)
  • Firefox: 128.0.3 (64-bit)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare the deployed example page with 1-js/03-code-quality/01-debugging-chrome/debugging.view/hello.js, which the issue identifies as the intended source. First inspect how that example is built or deployed, then verify the browser’s sources panel after a refresh. Done means the deployed example shows the nine-line source and matches the tutorial text.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.