@@ -28,7 +28,7 @@ PHP scripts**. With it on, PhpStorm stops at the first line of every request it
2828receives. That is occasionally useful and usually not what you want, especially
2929here, where every request arrives.
3030
31- [ Zero-configuration debugging] ( https://www.jetbrains.com/help/phpstorm/zero-configuration-debugging.html )
31+ ** JetBrains docs: ** [ Zero-configuration debugging] ( https://www.jetbrains.com/help/phpstorm/zero-configuration-debugging.html )
3232· [ Start a PHP debugging session] ( https://www.jetbrains.com/help/phpstorm/php-debugging-session.html )
3333
3434## Connecting to a client
@@ -59,7 +59,7 @@ session connects and the breakpoints are ignored. The
5959[ Docker] ( ../getting-started/docker.mdx ) page sets it alongside the debugger's own
6060settings.
6161
62- [ Configure Xdebug] ( https://www.jetbrains.com/help/phpstorm/configuring-xdebug.html )
62+ ** JetBrains docs: ** [ Configure Xdebug] ( https://www.jetbrains.com/help/phpstorm/configuring-xdebug.html )
6363
6464## Breakpoints
6565
@@ -73,7 +73,7 @@ PhpStorm's **Mute Breakpoints** button disables them all at once without deletin
7373them. It is handy mid-session, but muted breakpoints are still breakpoints as far as
7474the debugger is concerned — for the overhead to go away they have to be removed.
7575
76- [ Breakpoints] ( https://www.jetbrains.com/help/phpstorm/using-breakpoints.html )
76+ ** JetBrains docs: ** [ Breakpoints] ( https://www.jetbrains.com/help/phpstorm/using-breakpoints.html )
7777
7878## Step debugging
7979
@@ -89,7 +89,7 @@ which can skip library scripts and any scripts you list, and **PHP | Debug | Ste
8989Filters** , which can skip magic methods, constructors and named methods. ** Force
9090Step Into** ignores both for a single step.
9191
92- [ Step through the program] ( https://www.jetbrains.com/help/phpstorm/stepping-through-the-program.html )
92+ ** JetBrains docs: ** [ Step through the program] ( https://www.jetbrains.com/help/phpstorm/stepping-through-the-program.html )
9393
9494## Inspect variables
9595
@@ -102,7 +102,7 @@ the part worth getting into the habit of using.
102102PhpStorm also shows values inline, greyed out beside the code itself, which often
103103saves going to the panel at all.
104104
105- [ Examine a suspended program] ( https://www.jetbrains.com/help/phpstorm/examining-suspended-program.html )
105+ ** JetBrains docs: ** [ Examine a suspended program] ( https://www.jetbrains.com/help/phpstorm/examining-suspended-program.html )
106106
107107## Watches and edits
108108
@@ -115,7 +115,7 @@ warnings about side effects apply exactly as written.
115115To change a value, double-click it in the variables pane, or use ** Set Value** from
116116its context menu.
117117
118- [ Evaluate expressions] ( https://www.jetbrains.com/help/phpstorm/evaluating-expressions.html )
118+ ** JetBrains docs: ** [ Evaluate expressions] ( https://www.jetbrains.com/help/phpstorm/evaluating-expressions.html )
119119
120120## Logging
121121
@@ -125,7 +125,7 @@ The Console tab of the Debug tool window carries your script's output, and PHP's
125125warnings and notices appear there as the request produces them. Nothing needs
126126enabling on our side; PhpStorm asks for both when the session opens.
127127
128- [ Debug tool window: Console] ( https://www.jetbrains.com/help/phpstorm/debug-tool-window-console.html )
128+ ** JetBrains docs: ** [ Debug tool window: Console] ( https://www.jetbrains.com/help/phpstorm/debug-tool-window-console.html )
129129
130130## Troubleshooting
131131
@@ -137,4 +137,4 @@ code runs. Our [troubleshooting page](../user-guide/troubleshooting.md) covers t
137137debugger side, and the debug log at the default level will tell you whether a
138138connection was attempted and where to.
139139
140- [ Troubleshooting PHP debugging] ( https://www.jetbrains.com/help/phpstorm/troubleshooting-php-debugging.html )
140+ ** JetBrains docs: ** [ Troubleshooting PHP debugging] ( https://www.jetbrains.com/help/phpstorm/troubleshooting-php-debugging.html )
0 commit comments