Watch the VSCode Debugger Video
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 1/5
- Geschätzter Aufwand
- Unter einer Stunde
- Anfängerfreundlichkeit
- 78/100
- Issue-Typ
- Dokumentation
- Klarheit
- Klar beschrieben
- Aktivitätsstatus
- Veraltet
- Tech-Stack
- javascript, vscode
- Bereich
- documentation
Rechercherichtung
Beginne mit dem verlinkten VSCode-Debugging-Kurs und sieh dir die ersten vier Minuten des Videos an. Erkunde dann den VSCode Debugger auf deinem Rechner anhand eines einfachen Node-Skripts mit einem Fehler, indem du Breakpoints setzt und die Ausführung schrittweise durchgehst. Erledigt bedeutet, dass du die Debugger-Tools kennengelernt und das Lernziel erreicht hast.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- JavaScript
- Sterne
- 0
- Forks
- 397
- Ø Merge
- 1 Min.
- Gemergte PRs (30 T.)
- 1
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus CodeYourFuture/Module-Structuring-and-Testing-Data
-
🏕 Priority Mandatory 📅 Sprint 1 Core Submit:None
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 68/100
-
🏕 Priority Mandatory 📅 Sprint 3 Core Module-Structuring-And-Testing-Data Submit:None 🦔 Size Tiny
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 85/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Submit:PR
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 72/100
-
:gear: bug 📅 Sprint 3 Module-Structuring-And-Testing-Data NotCoursework
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 50/100
-
🏕 Priority Mandatory 📅 Sprint 1 Core Module-Structuring-And-Testing-Data Submit:None 🦔 Size Tiny
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 35/100
Alle Issues in CodeYourFuture/Module-Structuring-and-Testing-Data
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
-
Theme loads third-party resources on every page (jsdelivr web font, cdnjs Font Awesome) – GDPR Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
docToolchain/docToolchain#1705 ·
-
Timezone select lists one option per character; duplicate "Failed" reason; shared tracker popover id Offenbug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
nightscout/nocturne#1414 ·
-
bug v2
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
modelcontextprotocol/inspector#2458 · 1 Kommentar ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
carbon-design-system/ibm-products#9907 ·