Remove Deprecated Class+Interface from Map of Compiled Classes #14831
Labels
Comments
This was referenced Jun 2, 2015
fabpot
added a commit
that referenced
this issue
Jun 2, 2015
…(Zander Baldwin) This PR was merged into the 2.7 branch. Discussion ---------- [2.7][SecurityBundle] Remove SecurityContext from Compile | Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | no change | Fixed tickets | #14831 | License | MIT | Doc PR | n/a Remove the deprecated [SecurityContext](https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Security/Core/SecurityContext.php) from the list of classes to compile into `classes.map` and `classes.php`. Prevents `E_USER_DEPRECATED` notices from being thrown on every request. Commits ------- 1778e02 [2.7][SecurityBundle] Remove SecurityContext from Compile
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the security bundle's extension class for Symfony
v2.7.0(and apparently still inmasterand2.7branches) there is still a reference toSymfony\Component\Security\Core\SecurityContextin a call toaddClassesToCompile()on line 103 in filesrc/Symfony/Bundle/SecurityBundle/DependencyInjection/SecurityExtension.php.Due to
SexurityContextbeing included in the compiledclasses.mapandclasses.php, two deprecated errors are thrown on every request (an extra one is thrown due to the inclusion ofSecurityContextInterfacewhichSecurityContextimplements).The text was updated successfully, but these errors were encountered: