[NodeBundle] Deprecate unused TemplateEngine constructor argument #2073
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.
This was a left over of the clean up in PR #544. I've deprecated the unused
$templating
argument so it can be removed in the next major.I wanted to add a test to check the deprecation behavior. But this is not possible because we run our tests with codeception. (see explanation below)
The test checks the deprecation behavior by using the
@expectedDeprecation
annotation provided bysymfony/phpunit-bridge
. This annotation allows to test classes if they throw the correct deprecation warning. But in the current codeception setup it's not possible to use this listener as codeception doesn't usethe phpunit.xml
(where you should register the phpunit-bridge listener) or you have no option to manually set the listener in the codeception config.Is it even necessary to run our testsuite with codeception? As we currently only have phpunit tests and integration tests can easily be done with behat (as it is already the case on the standard-edition). I would suggest to switch back to phpunit as we can cover all our cases with phpunit and have the extra test helpers from the
symfony/phpunit-bridge