[Security] Fix TraceableAccessDecisionManager / DebugAccessDecisionManager BC layer #22664
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Same as #22657 for the renaming of
DebugAccessDecisionManager
intoTraceableAccessDecisionManager
. Indeed, I think we also require to redeclare the oldDebugAccessDecisionManager
for composerclassmap-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 ofDefinitionDecorator
.