…ston-thumbtack)This PR was merged into the 3.4 branch.Discussion----------[VarDumper] Added setMinDepth to VarClonerThis new function allows VarCloner users to specify a minimum treedepth that must be fully explored before we start limiting the number ofcloned items via the existing setMaxItems functionality.It’s useful for dumping arguments from a backtrace to ensure someminimum level of detail, while keeping a very low setMaxItems value toensure fast performance at the deeper levels.| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | no| New feature?  | yes <!-- don't forget updating src/**/CHANGELOG.md files -->| BC breaks?    | no| Deprecations? | no <!-- don't forget updating UPGRADE-*.md files -->| Tests pass?   | yes| Fixed tickets | none| License       | MIT| Doc PR        |symfony/symfony-docs#8155 <!--highly recommended for new features--><!--- Bug fixes must be submitted against the lowest branch where they apply  (lowest branches are regularly merged to upper ones so they get the fixes too).- Features and deprecations must be submitted against the 3.4,  legacy code removals go to the master branch.- Please fill in this template according to the PR you're about to submit.- Replace this comment by a description of what your PR is solving.-->Commits-------d6534f5 [VarDumper] Added setMinDepth to VarCloner

The Symfony VarDumper component includes an HtmlDumper that dumpsvariables in a rich HTML format that allows for expanding and collapsingindividual tree nodes in the dumped variable.  This makes it much morepractical to navigate large/deep variables that have been dumped.DebugBarVarDumper provides a Debug Bar-friendly wrapper around theVarDumper component.  It’s intended as a better alternative toDataFormatter::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.0All seem to work fine, with graceful degradation as needed.Furthermore, the class is ready to take advantage of new features that Iadded and are upcoming in Symfony v3.4:* setMinDepth:symfony/symfony#23515  This feature will be valuable for the upcoming BacktraceCollector.

The Symfony VarDumper component includes an HtmlDumper that dumpsvariables in a rich HTML format that allows for expanding and collapsingindividual tree nodes in the dumped variable.  This makes it much morepractical to navigate large/deep variables that have been dumped.DebugBarVarDumper provides a Debug Bar-friendly wrapper around theVarDumper component.  It’s intended as a better alternative toDataFormatter::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.0All seem to work fine, with graceful degradation as needed.Furthermore, the class is ready to take advantage of new features that Iadded and are upcoming in Symfony v3.4:* setMinDepth:symfony/symfony#23515  This feature will be valuable for the upcoming BacktraceCollector.

The Symfony VarDumper component includes an HtmlDumper that dumpsvariables in a rich HTML format that allows for expanding and collapsingindividual tree nodes in the dumped variable.  This makes it much morepractical to navigate large/deep variables that have been dumped.DebugBarVarDumper provides a Debug Bar-friendly wrapper around theVarDumper component.  It’s intended as a better alternative toDataFormatter::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.0All seem to work fine, with graceful degradation as needed.Furthermore, the class is ready to take advantage of new features that Iadded and are upcoming in Symfony v3.4:* setMinDepth:symfony/symfony#23515  This feature will be valuable for the upcoming BacktraceCollector.

The Symfony VarDumper component includes an HtmlDumper that dumpsvariables in a rich HTML format that allows for expanding and collapsingindividual tree nodes in the dumped variable.  This makes it much morepractical to navigate large/deep variables that have been dumped.DebugBarVarDumper provides a Debug Bar-friendly wrapper around theVarDumper component.  It’s intended as a better alternative toDataFormatter::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.0All seem to work fine, with graceful degradation as needed.Furthermore, the class is ready to take advantage of new features that Iadded and are upcoming in Symfony v3.4:* setMinDepth:symfony/symfony#23515  This feature will be valuable for the upcoming BacktraceCollector.

The Symfony VarDumper component includes an HtmlDumper that dumpsvariables in a rich HTML format that allows for expanding and collapsingindividual tree nodes in the dumped variable.  This makes it much morepractical to navigate large/deep variables that have been dumped.DebugBarVarDumper provides a Debug Bar-friendly wrapper around theVarDumper component.  It’s intended as a better alternative toDataFormatter::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.0All seem to work fine, with graceful degradation as needed.Furthermore, the class is ready to take advantage of new features that Iadded and are upcoming in Symfony v3.4:* setMinDepth:symfony/symfony#23515  This feature will be valuable for the upcoming BacktraceCollector.