-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Removed deprecated features and notices #8622
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I'll take a look on Monday |
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.
Left comments, but can be done after merging.
@@ -129,17 +129,10 @@ read more about it, see the ":doc:`/bundles/configuration`" article. | |||
Adding Classes to Compile | |||
------------------------- | |||
|
|||
.. versionadded:: 3.3 | |||
This technique is discouraged and the ``addClassesToCompile()`` method was | |||
deprecated in Symfony 3.3 because modern PHP versions make it unnecessary. |
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.
Unless I'm wrong, this versionadded says "Don't use what's descriped below." (so it's more a .. caution::
than versionadded). This means the article should be removed (as the feature got removed in Symfony 4).
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.
I though the same ... but only addClassesToCompile()
is deprecated/removed. addAnnotatedClassesToCompile()
is still valid and used in Sf4.
bundles/override.rst
Outdated
third-party bundles without using :doc:`/bundles/inheritance`, which is | ||
deprecated since Symfony 3.4. | ||
third-party bundles without using :doc:`/bundles/inheritance`, which was | ||
removed in Symfony 4.0. |
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.
Let's make this description generic to not require any more updates in later versions (and thus merge conflicts), e.g:
When using another bundle, you might want to customize or override some of its features. This document describes ways of overriding the most common features of a bundle.
components/console/events.rst
Outdated
|
||
Listeners receive a | ||
:class:`Symfony\\Component\\Console\\Event\\ConsoleExceptionEvent` event:: | ||
|
||
use Symfony\Component\Console\Event\ConsoleExceptionEvent; | ||
use Symfony\Component\Console\ConsoleEvents; | ||
|
||
$dispatcher->addListener(ConsoleEvents::EXCEPTION, function (ConsoleExceptionEvent $event) { | ||
$dispatcher->addListener(ConsoleEvents::ERROR, function (ConsoleExceptionEvent $event) { |
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.
Typehint should be ConsoleErrorEvent
components/console/events.rst
Outdated
@@ -117,19 +114,6 @@ Listeners receive a | |||
$event->setException(new \LogicException('Caught exception', $exitCode, $event->getException())); |
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.
$event->getError()
} | ||
} | ||
The ``ContainerAwareEventDispatcher`` was removed in Symfony 4.0. Use | ||
``EventDispatcher`` with closure-proxy injection instead. |
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.
reference article/section about closure-proxy injection?
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.
I don't understand this comment. Is there an article that we could link to in this comment? Or are you suggesting to create a new article? Thanks!
profiler/matchers.rst
Outdated
), | ||
)); | ||
The possibility to use a matcher to enable the profiler conditionally was | ||
removed in Symfony 4.0. |
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.
We should add information about doing $profiler->disable()
in your controller explicitly if you need this functionality.
+1 for removing |
… weaverryan) This PR was merged into the master branch. Discussion ---------- Removed deprecated features and notices @xabbuh and @weaverryan to avoid a nightmare or rebases and problems, could we please give top priority to merging this PR? Thanks! It doesn't have to be perfect or 100% completed. We can do more fixes in another PR. Thanks! ----- Some articles explain things that are removed. Instead of removing those articles entirely and to avoid user confusion, I propose to keep those articles but explain that those features no longer exist. For example, `security/acl.rst` now contains the following: ```rst .. index:: single: Security; Access Control Lists (ACLs) How to Use Access Control Lists (ACLs) ====================================== .. caution:: ACL support was removed in Symfony 4.0. Install the `Symfony ACL bundle`_ and refer to its documentation if you want to keep using ACL. .. _`Symfony ACL bundle`: https://github.com/symfony/acl-bundle ``` Articles like this one: * security/acl.rst * security/acl_advanced.rst * components/event_dispatcher/container_aware_dispatcher.rst We can remove all these deprecated articles in 4.1 ----- @iltar could you please create a PR to update the changes related to "controller arguments" in these two articles? Thanks! * `components/http_kernel.rst` * `create_framework/http_kernel_controller_resolver.rst` I don't understand the changes well (`ControllerResolverInterface` removed `getArguments()`) ----- @HeahDude could you please create a PR to update the changes needed about the deprecation of using `false` in `property_path` instead of `mapped` in `reference/forms/types/options/property_path.rst.inc`? Thanks! ----- There is a pending deprecation message in `security/multiple_user_providers.rst` ... but that's fixed in the pending PR #8612. ----- A final question: I've removed the explanation of the deprecated `kernel.root_dir` in `reference/configuration/kernel.rst` and kept only `kernel.project_dir`. Would you instead prefer to keep a reference to the still heavily used `kernel.root_dir` to explain that it's deprecated? Commits ------- 02c676a fixing old reference eb53f14 Fixing test failure 47a224a Fixed ater Wouter's review 597b75b Removed more references about profiler.matcher option 0266046 Removed deprecated features and notices
I've just merged this so we can keep conflicts low and keep moving quickly (thanks Wouter for the fast review). I did get the tests passing. If anyone does see any issues, please open a separate PR! @javiereguiluz can you open separate issues on the 4.0 milestone for the other things that you needed done by other people? Thanks! |
Done! Thanks for your great and quick reviews and for merging this. Cheers! |
@xabbuh and @weaverryan to avoid a nightmare or rebases and problems, could we please give top priority to merging this PR? Thanks! It doesn't have to be perfect or 100% completed. We can do more fixes in another PR. Thanks!
Some articles explain things that are removed. Instead of removing those articles entirely and to avoid user confusion, I propose to keep those articles but explain that those features no longer exist. For example,
security/acl.rst
now contains the following:Articles like this one:
We can remove all these deprecated articles in 4.1
@iltar could you please create a PR to update the changes related to "controller arguments" in these two articles? Thanks!
components/http_kernel.rst
create_framework/http_kernel_controller_resolver.rst
I don't understand the changes well (
ControllerResolverInterface
removedgetArguments()
)@HeahDude could you please create a PR to update the changes needed about the deprecation of using
false
inproperty_path
instead ofmapped
inreference/forms/types/options/property_path.rst.inc
? Thanks!There is a pending deprecation message in
security/multiple_user_providers.rst
... but that's fixed in the pending PR #8612.A final question: I've removed the explanation of the deprecated
kernel.root_dir
inreference/configuration/kernel.rst
and kept onlykernel.project_dir
. Would you instead prefer to keep a reference to the still heavily usedkernel.root_dir
to explain that it's deprecated?