<table role="table">
<thead>
<tr>
<th>Q</th>
<th>A</th>
</tr>
</thead>
<tbody>
<tr>
<td>Bug report?</td>
<td>no</td>
</tr>
<tr>
<td>Feature request?</td>
<td>yes</td>
</tr>
<tr>
<td>BC Break report?</td>
<td>yes/no</td>
</tr>
<tr>
<td>RFC?</td>
<td>yes/no</td>
</tr>
<tr>
<td>Symfony version</td>
<td>4.*</td>
</tr>
</tbody>
</table>
<p dir="auto">Debug code leftover in production is smelly, but there are cases where this occurs (for example you are debugging somethin in production and you run the same codebase in development and production mode on different ports or domains).</p>
<p dir="auto">In such a case it would help alot if the <code class="notranslate">dump</code> function would be replaced with an empty stub (or something that sends warning messages to the logger that there is a forgotten <code class="notranslate">dump</code> function in the code) to not exit at this position with an "call to undefined function".</p>
<table role="table">
<thead>
<tr>
<th>Q</th>
<th>A</th>
</tr>
</thead>
<tbody>
<tr>
<td>Bug report?</td>
<td>no</td>
</tr>
<tr>
<td>Feature request?</td>
<td>yes</td>
</tr>
<tr>
<td>BC Break report?</td>
<td>no</td>
</tr>
<tr>
<td>RFC?</td>
<td>no</td>
</tr>
<tr>
<td>Symfony version</td>
<td>3.2</td>
</tr>
</tbody>
</table>
<p dir="auto">I'm very addicted to dump() to debug my code and i find it a invaluable tool, so thank you very much!<br>
Unfortunately some time i forget to rid off of a dump or two in the code and if the code bump into production i got an exception because dump() does not exists.</p>
<p dir="auto">I understand this should not happen and i should get more controls in place, but it happens; so my proposal: why not create a fake dump() function for production environment that does absolutely nothing?</p>
<p dir="auto">Regards,<br>
Matteo</p>