Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
bug #22664 [Security] Fix TraceableAccessDecisionManager / DebugAcces…
…sDecisionManager BC layer (ogizanagi) This PR was merged into the 3.3-dev branch. Discussion ---------- [Security] Fix TraceableAccessDecisionManager / DebugAccessDecisionManager BC layer | Q | A | ------------- | --- | Branch? | 3.3 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #22657 (comment) | License | MIT | Doc PR | N/A Same as #22657 for the renaming of `DebugAccessDecisionManager` into `TraceableAccessDecisionManager`. Indeed, I think we also require to redeclare the old `DebugAccessDecisionManager` for composer `classmap-authoritative` autoloading strategy & classmap dumper. AppVeyor failures unrelated. Edit: Re-thinking about it, it's probably not very common to dump the classmap and use the `classmap-authoritative` strategy when using those classes... That's to say: in debug mode/dev env. So it may be the reason why the class wasn't redeclared on contrary of `DefinitionDecorator`. Commits ------- 5b123b9 [Security] Fix TraceableAccessDecisionManager / DebugAccessDecisionManager BC layer
- Loading branch information