Skip to content

[FrameworkBundle][Routing] Move RoutingResolverPass to the Routing component #21835

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

Merged
merged 1 commit into from
Mar 5, 2017

Conversation

chalasr
Copy link
Member

@chalasr chalasr commented Mar 2, 2017

Q A
Branch? master
Bug fix? no
New feature? yes
BC breaks? no
Deprecations? yes
Tests pass? yes
Fixed tickets n/a
License MIT
Doc PR n/a

use Symfony\Component\DependencyInjection\Reference;
use Symfony\Component\DependencyInjection\ContainerBuilder;
use Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface;
@trigger_error(sprintf('The %s class is deprecated since version 3.3 and will be removed in 4.0. Use Symfony\Component\Routing\DependencyInjection\RoutingResolverPass instead.', RoutingResolverPass::class), E_USER_DEPRECATED);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can move that line below the "use" and use BaseRoutingResolverPass::class in sprintf

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I wasn't sure if having it immediately after the namespace has an importance

@@ -23,6 +23,7 @@
"symfony/http-foundation": "~2.8|~3.0",
"symfony/yaml": "~2.8|~3.0",
"symfony/expression-language": "~2.8|~3.0",
"symfony/dependency-injection": "~2.7|~3.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2.8 instead of 2.7

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@chalasr chalasr force-pushed the routingresolverpass branch from 7135861 to 7d062fb Compare March 3, 2017 09:26
Copy link
Member

@nicolas-grekas nicolas-grekas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@chalasr chalasr force-pushed the routingresolverpass branch 2 times, most recently from 7f9ce37 to 8b04332 Compare March 3, 2017 12:51
@nicolas-grekas nicolas-grekas added this to the 3.3 milestone Mar 4, 2017
class RoutingResolverPass implements CompilerPassInterface
{
private $resolverServiceId = 'routing.resolver';
private $loaderTag = 'routing.loader';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

default values could be removed here, would prevent a duplication and any sync mistake

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's a mistake, fixed. Thanks

@chalasr chalasr force-pushed the routingresolverpass branch from 8b04332 to 32be16b Compare March 5, 2017 15:12
@fabpot
Copy link
Member

fabpot commented Mar 5, 2017

Thank you @chalasr.

@fabpot fabpot merged commit 32be16b into symfony:master Mar 5, 2017
fabpot added a commit that referenced this pull request Mar 5, 2017
… the Routing component (chalasr)

This PR was merged into the 3.3-dev branch.

Discussion
----------

[FrameworkBundle][Routing] Move RoutingResolverPass to the Routing component

| Q             | A
| ------------- | ---
| Branch?       | master
| Bug fix?      | no
| New feature?  | yes
| BC breaks?    | no
| Deprecations? | yes
| Tests pass?   | yes
| Fixed tickets | n/a
| License       | MIT
| Doc PR        | n/a

Commits
-------

32be16b Move RoutingResolverPass to the Routing component
@fabpot fabpot mentioned this pull request May 1, 2017
@chalasr chalasr deleted the routingresolverpass branch May 10, 2017 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants