Inspect runtime values and types with var_dump, print_r and get_debug_type to find unexpected shapes.
What It Does
Check both content and runtime type. Inspect a small collection safely.
Requirements and Compatibility
Use a supported PHP runtime and install any third-party tool or extension explicitly shown in the examples. Commands should be run from the project root unless stated otherwise.
Syntax, Inputs and Results
The examples separate configuration, the smallest working operation and a realistic follow-up task. Adapt file paths and dependency versions to your own project.
Example 1: Basic Use
Check both content and runtime type.
<?php
$account = ['id' => 82, 'verified' => true];
var_dump($account['verified']);
echo get_debug_type($account);Example 2: Another Case
Inspect a small collection safely.
<?php
$rows = [['sku' => 'P1'],['sku' => 'P2']];
print_r(array_column($rows,'sku'));
echo count($rows);Practical Example
Redact credential fields before logging.
<?php
$request = ['token' => 'secret', 'page' => 3];
$safe = array_diff_key($request, array_flip(['token']));
error_log(json_encode($safe, JSON_THROW_ON_ERROR));For production, apply the compatibility and edge-case limits described below.
Important Behavior and Edge Cases
Never expose passwords, tokens or private fields in a public error response or shared log.
Comparison with Related Functions and Tools
| Subject | Key difference |
|---|---|
| Step debugging vs profiling | Step debugging pauses individual statements; profiling records aggregate runtime cost. |
Common Beginner Mistakes
| Mistake | Correct approach |
|---|---|
| Enabling the debugger for every production request | Use controlled triggers and disable development modes in production. |
| Skipping the prerequisite of this specific workflow | Install or configure the named tool and confirm the example can actually run. |
| Ignoring edge conditions | Never expose passwords, tokens or private fields in a public error response or shared log. |
Key Takeaways
- Inspect runtime values and types with var_dump, print_r and get_debug_type to find unexpected shapes.
- Never expose passwords, tokens or private fields in a public error response or shared log.
- Keep application configuration, source code and validation tests under version control.
Use these examples as a starting point, then validate the result with the actual PHP build, dependencies and inputs used by your application.