Watch the VSCode Debugger Video

オープン
#2 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
1/5
見積もり時間
1時間未満
初心者へのやさしさ
78/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
停滞
技術スタック
javascript, vscode
領域
documentation

調査の方向性

リンクされているVSCodeデバッグのコースから始め、動画の最初の4分間を視聴してください。次に、バグのあるシンプルなNodeスクリプトを使って、ブレークポイントを設定し、実行をステップ実行しながら、自分のマシン上でVSCode Debuggerを試してください。完了とは、デバッガーツールを学び、学習目標を達成した状態を指します。

索引モデルが issue の本文から書いたものです。

説明

🏝️ Priority Stretch 📅 Sprint 3 Module-Structuring-And-Testing-Data Optional Submit:None 🦔 Size Tiny
Learning Objectives
  • Learn about the debugging tools built into VSCode
Link to the coursework

https://code.visualstudio.com/docs/introvideos/debugging

Why are we doing this?

🧰 We are building a toolkit to help us write great software. In our toolkit we are collecting skills with:

📝 Specifications, like user stories, acceptance criteria, and Given/When/Then
Help us understand what to write and check we've written the right thing.

🧪 Tests, like unit tests and assertions
Help us break down our problems and check our solutions work even when we change things.

💬 Asking questions
Helps us formally reason through our problems and identify gaps in our mental models.

🤖Playing computer
Helps us reason about code with a mental model.

🦺 Audits, like Lighthouse
Help us identify performance and quality improvements we can make to our code.

And now we can add debuggers to our toolkit.

🐛 Debuggers are tools that help us find and fix problems, or bugs, in our JavaScript code. They let us step through our code line-by-line while it runs to see what is happening. This helps us find the place where our mental model of the code is different from our implementation. Your browser has a debugger and so does VSCode.

Key reasons we use debuggers:

  • See what's happening inside functions
  • Check if variables have expected values
  • Pause execution and step through slowly
  • Find exactly where mistakes happen

JavaScript debuggers give control over execution flow to methodically test and fix bugs. Watch the first four minutes of the video and then explore the VSCode Debugger on your machine.

Maximum time in hours

.5

How to get help

AI can help you here. Code along with AI so it has the context and ask it when you get stuck. Use this starting prompt:

Act as a friendly, supportive, knowledgeable programming mentor. I am learning the debugger in VSCode.Talk me through the interface step by step. Provide a simple example of a Node script with a bug in it and walk me through finding the bug by setting breakpoints with the debugger. Don't tell me what the bug is. When I get stuck, answer my questions in CEFR B2 English meant for an adult professional speaking in a second language. When I ask for hints, give me useful pointers. Say okee dokee if you understand and begin your walkthrough.

Remember to use careful prompting when you don't understand, so you get real learning out of the exchange. Say things like:

The execution is paused and it shows me that is undefined and is undefined, but I don't understand why it says that. Can you explain this to me?

And remember you should always ask your friendly humans in Slack when you get really stuck. This coursework will be set again in later modules, so if it's beyond you right now, you'll pick it up later.

主要言語
JavaScript
スター
0
フォーク
397
PR マージ指標
30日以内にマージされた PR はありません

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

CodeYourFuture/Module-Structuring-and-Testing-Data のほかの issue

CodeYourFuture/Module-Structuring-and-Testing-Data の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。