This repository has been archived on 2023-08-20. You can view files and clone it, but cannot push or open issues or pull requests.

Fabien Potencier 5dcd82ca28 minor #24829 [SecurityBundle] Fix the datacollector to properly support decision.object being null (ogizanagi) ... 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 <!-- see comment below --> | Bug fix? | yes | New feature? | no <!-- don't forget to update src/**/CHANGELOG.md files --> | BC breaks? | no | Deprecations? | no <!-- don't forget to update UPGRADE-*.md files --> | Tests pass? | yes | Fixed tickets | #24804 <!-- #-prefixed issue number(s), if any --> | License | MIT | Doc PR | N/A Similar to https://github.com/symfony/symfony/pull/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 ------- 769a5f204f [SecurityBundle] Fix the datacollector to properly support decision.object being null		2017-11-06 01:14:54 -08:00
..
Symfony	minor #24829 [SecurityBundle] Fix the datacollector to properly support decision.object being null (ogizanagi)	2017-11-06 01:14:54 -08:00