minor #24829 [SecurityBundle] Fix the datacollector to properly support decision.object being null (ogizanagi)

fabpot · fabpot · commit 5dcd82ca2818 · 2017-11-06T01:14:54.000-08:00
This PR was merged into the 3.3 branch. Discussion ---------- [SecurityBundle] Fix the datacollector to properly support decision.object being null | Q | A | ------------- | --- | Branch? | 3.3  | Bug fix? | yes | New feature? | no  | BC breaks? | no | Deprecations? | no  | Tests pass? | yes | Fixed tickets | #24804  | License | MIT | Doc PR | N/A Similar to #23050, when accessing a `Data` clone property through `__get()` and the value is `null` for instance, you'll really get `null` instead of a `Data` instance. The solution is to use `seek` instead whenever we access and try to use `profiler_dump` on a `Data` property that can be a simple scalar like `null` or `false`. AFAIK, `decision.object` is the only one here. Commits ------- 769a5f2 [SecurityBundle] Fix the datacollector to properly support decision.object being null
diff --git a/src/Symfony/Bundle/SecurityBundle/Resources/views/Collector/security.html.twig b/src/Symfony/Bundle/SecurityBundle/Resources/views/Collector/security.html.twig
@@ -264,7 +264,7 @@
                                 {{ profiler_dump(decision.attributes) }}
                             {% endif %}
                         </td>
-                        <td>{{ profiler_dump(decision.object) }}</td>
+                        <td>{{ profiler_dump(decision.seek('object')) }}</td>
                     </tr>
                 {% endfor %}
             </tbody>
