Appearance

TL;DR

Short, practical steps to inspect the Basket controller using the Symfony Profiler (dump) and Xdebug (step debugging).

Quick primer ​

  • dump() / var_dump() — non‑fatal inspection; dumped values appear in the Web Profiler under the "Debug" panel. Use this for interactive checks.
  • dd() — dump and die; stops execution and is destructive (use sparingly).
  • Xdebug — step through code line by line in your IDE, inspect any variable at any point, no code changes needed. See Xdebug (step debugging) below.

Note: the Web Profiler / dump integration is only available for HTTP requests in the dev environment — it does not help with CLI commands or background jobs. Xdebug works for both.

Example: inspecting a controller variable ​

TIP

Foodsharing\Modules\Basket\BasketController::basket(int $id) is used below purely as an example. The same dump() approach works in any controller or service.

Goal ​

See what $basket contains.

Profiler (fast) ​

Add a temporary dump right after $basket is loaded in basket():

php
$basket = $this->basketGateway->getBasket($id);
dump($basket); // appears in Profiler -> "Debug"
dump('Second dump'); // multiple dumps are supported (e.g. dump($requests))

Reproduce: open /essenskoerbe/{id} in your browser and inspect the Profiler (Web Debug Toolbar → Profiler → Debug).

Profiler Debug panel showing the dumped $basket object, collapsed

Click the ► markers to expand nested arrays and objects, e.g. contactTypes:

Profiler Debug panel with the contactTypes array expanded

Nested objects like location and creator expand the same way:

Profiler Debug panel with the nested location and creator objects expanded

dd() (dump and die) ​

Use dd() instead of dump() when you want to see the value immediately, without opening the Profiler — it prints the dump directly to the page and halts execution:

php
$basket = $this->basketGateway->getBasket($id);
dd($basket); // prints directly to the response and stops here

TIP

dd() sends an HTTP 500 response and never reaches the rest of basket() — the request never finishes normally, so nothing shows up in the Profiler for it. Use dump() if you still need the rest of the request to run.

Xdebug (step debugging) ​

Xdebug lets you set breakpoints in your IDE and step through the actual request line by line, inspecting every variable in scope — no dump() calls to add or remove. It's the right tool when you need to see how a value changes across several steps, not just what it looks like at one point.

TIP

Full setup (PhpStorm config, the trigger/extension, per-platform Docker networking notes) is documented once in IDE Setup → Xdebug — this section only covers when to reach for it.

Quick PhpStorm rundown ​

  1. Install the Xdebug Helper browser extension (Chrome/Firefox) — one click per tab to turn debugging on/off for that tab.
  2. In PhpStorm, click "Start Listening for PHP Debug Connections".
  3. Set a breakpoint in e.g. BasketController::basket(), enable the extension, open /essenskoerbe/{id}.
  4. PhpStorm stops at the breakpoint with the full variable scope, call stack, and step controls (step over/into/out).

Profiler/dump() vs. Xdebug — which one? ​

Profiler / dump()Xdebug
Setup per useAdd/remove a line of codeNone — toggle the extension
ShowsOne or a few values, at the point you placed themEvery variable in scope, at any line you step to
Following control flowNo — you only see what you explicitly dumpedYes — step line by line, into function calls
Works for CLI / background jobsNo (Profiler is HTTP-only)Yes
Overhead when unusedNoneNone (this project uses mode=trigger — see IDE Setup)
Good for"What does this variable look like right here?" — quick, no IDE setup needed"Why does this branch/loop/value do that?" — following logic across multiple lines or calls

In short: reach for dump() first — it's faster for a single "what's in this variable" question. Reach for Xdebug when you need to actually follow the code's path (which if branch was taken, why a loop ran N times, what an object looked like three calls up the stack) rather than inspect one snapshot.

Cleanup & quick rules ​

  • Remove any dump() / dd() immediately after debugging — do not commit them.
  • Dumping larger structures is fine since the output is ephemeral and only visible in the dev Profiler.

References ​