Watch the VSCode Debugger Video
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 1/5
- Tempo stimato
- Meno di un'ora
- Idoneità per principianti
- 78/100
- Tipo di issue
- Documentazione
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Ferma
- Stack tecnologico
- javascript, vscode
- Ambito
- documentation
Direzione di ricerca
Inizia con il corso di debugging di VSCode collegato e guarda i primi quattro minuti del video. Poi esplora il VSCode Debugger sulla tua macchina usando un semplice script Node con un bug, impostando breakpoint ed eseguendo il codice passo dopo passo. Il lavoro è completato quando hai imparato a usare gli strumenti del debugger e raggiunto l’obiettivo di apprendimento.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- JavaScript
- Stelle
- 0
- Fork
- 397
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di CodeYourFuture/Module-Structuring-and-Testing-Data
-
🏕 Priority Mandatory 📅 Sprint 1 Core Submit:None
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 68/100
-
Complete the mid-way survey Aperta🏕 Priority Mandatory 📅 Sprint 3 Core Module-Structuring-And-Testing-Data Submit:None 🦔 Size Tiny
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Submit:PR
Difficoltà 3/5 1-2 giorni Idoneità per principianti 72/100
-
:gear: bug 📅 Sprint 3 Module-Structuring-And-Testing-Data NotCoursework
Difficoltà 2/5 1-3 ore Idoneità per principianti 50/100
-
🏕 Priority Mandatory 📅 Sprint 1 Core Module-Structuring-And-Testing-Data Submit:None 🦔 Size Tiny
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 35/100
Tutte le issue di CodeYourFuture/Module-Structuring-and-Testing-Data
Issue simili
-
ai-observability bug team/ai-observability
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
AllTheMods/ATM-10-L#19 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
SignalK/n2k-signalk#345 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
-
Difficoltà 1/5 1-3 ore Idoneità per principianti 88/100
JuliaPluto/PlutoPlotly.jl#72 ·