Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
Removed deprecated contents#11621
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Removed deprecated contents#11621
Uh oh!
There was an error while loading.Please reload this page.
Conversation
wouterj left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Very nice job!
| the controller can be accessed by anonymous users. It requires installing | ||
| the:doc:`Security component</components/security>`. | ||
| :class:`Symfony\\Bundle\\SecurityBundle\\SecurityUserValueResolver` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Wow (unrelated to this PR), this is such an implementation detail that I would even vote to completely remove it from 4.2 docs (and just replace the class name and act like nothing changed, it doesn't matter for a framework user)
…aviereguiluz)This PR was squashed before being merged into the 4.3 branch (closes#11623).Discussion----------Deprecate the templating.* options of FrameworkBundleWe're correctly removing them in 5.0 (#11621) but we forgot to add the deprecation notice in 4.3.Commits-------29b46ec Deprecate the templating.* options of FrameworkBundle
This is related to#11620 and removes deprecated things.
The only remaining deprecation is the
transChoice()method. I'm leaving that for future PRs because@wouterj created a big PR pending to be merged related to that.