The Symfony VarDumper component includes an HtmlDumper that dumps variables in a rich HTML format that allows for expanding and collapsing individual tree nodes in the dumped variable. This makes it much more practical to navigate large/deep variables that have been dumped. DebugBarVarDumper provides a Debug Bar-friendly wrapper around the VarDumper component. It’s intended as a better alternative to DataFormatter::formatVar. It provides for: * Debug Bar-friendly styles for the VarDumper HTML. * Implements AssetProvider for returning VarDumper static assets (requires users of JavascriptRenderer to support inline assets). * Simplifies VarCloner and HtmlDumper function calls for cloning and dumping variables in a Debug Bar environment. VarDumper was originally written/targeted to be a replacement for var_dump, so the default behavior of HtmlDumper echoing static assets and variable dumps directly to the page output isn’t really appropriate. Furthermore, we must contend with several different Symfony versions going back to v2.6.0. This class provides a friendly wrapper. I have tested this with these Symfony versions: * v2.6.0 * v2.7.0 * v2.8.0 * v3.0.0 * v3.1.0 * v3.2.0 * v3.3.0 All seem to work fine, with graceful degradation as needed. Furthermore, the class is ready to take advantage of new features that I added and are upcoming in Symfony v3.4: * setMinDepth: https://github.com/symfony/symfony/pull/23515 This feature will be valuable for the upcoming BacktraceCollector.
5.2 KiB
Data Formatter
HTML variable formatting
PHP Debug Bar integrates with Symfony's
VarDumper component to provide
interactive HTML-based variable dumps. This is accomplished via the
DebugBar\DataFormatter\DebugBarVarDumper
class, which wraps VarDumper functionality for use by the
debug bar.
Debug bar users who wish to take advantage of this feature must ensure that they properly render inline assets when rendering the debug bar. That's because collectors using the variable dumper return the static assets of the HTML variable dumper, which includes inline assets.
By default, collectors inheriting from DebugBar\DataCollector\DataCollector
will use the
DebugBarVarDumper
instance specified by the static DataCollector::setDefaultVarDumper
function.
This can be overridden on a per-collector basis by the non-static DataCollector::setVarDumper
function.
// Modify default options used globally by all collectors
DataCollector::getDefaultVarDumper()->mergeClonerOptions(array(
'max_items' => 50,
));
// Modify options for a specific collector
$varDumper = new DebugBarVarDumper();
$varDumper->mergeDumperOptions(array(
'max_string' => 100,
));
$collector->setVarDumper($varDumper);
VarDumper has two key classes that are used by DebugBarVarDumper
. The options can be set using
the mergeClonerOptions
, resetClonerOptions
, mergeDumperOptions
, and resetDumperOptions
methods on DebugBarVarDumper
.
VarCloner
: Cloners copy the contents of a variable into a serializable format. They are intended to run as fast as possible; advanced rendering/formatting is saved for the dumper. Classes known as casters control how particular data types are serialized; if no caster exists, then a generic serialization is done. You can specify custom casters using theadditional_casters
option; the default list of casters can be overridden with thecasters
option. Finally, the number of items and maximum string length to clone can be controlled via themax_items
,min_depth
, andmax_string
options; consult the VarDumper documentation for more information on these options, which have a considerable performance impact. Note that themin_depth
option requires VarDumper 3.4 or newer.HtmlDumper
: Dumpers format cloned data for a particular destination, such as command-line or HTML.DebugBarVarDumper
only uses theHtmlDumper
. Custom styles can be specified via thestyles
option, but this is not generally needed. If using VarDumper 3.2 or newer, you may also specify theexpanded_depth
,max_string
, andfile_link_format
options.expanded_depth
controls the tree depth that should be expanded by default upon initial rendering.max_string
can be used to truncate strings beyond the initial truncation done by the cloner.file_link_format
is a format string used to generate links to source code files.
A collector wishing to take advantage of this feature must call the renderVar()
function and
return the HTML result as part of the request dataset:
public function collectVariable($v)
{
// This will clone and then dump the variable in one operation:
$this->variableHtml = $this->getVarDumper()->renderVar($v);
}
public function collect()
{
return array('variableHtml' => $this->variableHtml);
}
The collector may then render the raw HTML in a Javascript widget:
if (value.variableHtml) {
var val = $('<span />').html(value.variableHtml).appendTo(otherElement);
}
If the collector takes advantage of the variable dumper, as shown above, then it must also
implement the AssetProvider
interface and include the assets of the variable dumper. This does
not take place by default, because not all collectors will use the variable dumper.
class MyCollector extends DataCollector implements Renderable, AssetProvider
{
public function getAssets() {
return $this->getVarDumper()->getAssets();
}
}
You might want to clone a variable initially, and only dump it at a later time. This is supported by
the captureVar()
and renderCapturedVar()
functions. It's also possible to render only portions
of a cloned variable at a time.
$testData = array('one', 'two', 'three');
$cloned_variable = $this->getVarDumper()->captureVar($testData);
// Later, when you want to render it. Note the second parameter is $seekPath; here we specify
// to only render the second array element (index 1). $html will therefore only contain 'two'.
$html = $this->getVarDumper()->renderCapturedVar($cloned_variable, array(1));
Text formatting
An instance of DebugBar\DataFormatter\DataFormatterInterface
is used by collectors to
format variables into a text-only format.
The default instance is DebugBar\DataFormatter\DataFormatter
. This can be modified
using DebugBar\DataCollector\DataCollector::setDefaultDataFormatter()
.
You can use a custom formatter for each collector using DataCollector::setDataFormatter()
.
For general-purpose variable formatting, it's recommended to use the HTML variable dumper, described earlier.