Support for multiple routes

[dantleech]

Integrates: symfony-cmf/routing-auto#62

Note that this PR revealed a bug: #171 and I do not currently think it is related to this PR.

[dantleech]

Hmm .. this is 2.6 only, should I revert this..

[dantleech]

Failing on lowest dependencies because of deprecations: https://travis-ci.org/symfony-cmf/RoutingAutoBundle/jobs/97946914 /cc @wouterj

[wouterj]

@dantleech you have to use the new syntax wherever possible. For tests testing the BC layers, add /** @group legacy */ to the test class/test method.

[dantleech]

@wouterj would that fix the tests? they work in all other environments other than the --prefer-lowest one.

[wouterj]

@dantleech other tests are run with weak mode for deprecations (that's not really great, but let's change that in another PR), so deprecation notices won't show up as errors.

The problem is that many of the test fixtures still use strings for uri schema, e.g. https://github.com/symfony-cmf/RoutingAutoBundle/blob/multiple_routes/Tests/Resources/app/config/routing_auto.yml

[dantleech]

Yeah I can fix that, but the tests pass in all the other envs. I guess it is an earlier version of the deprecation code that makes it fail with the lowest deps? Will adding the @group legacy stop it failing?

[wouterj]

@dantleech tests pass in other envs, as the PHPUnit deprecation helper is set to weak.

We should avoid using deprecated things as much as possible, so please fix the test configuration :)

[dantleech]

Only one deprecation warning now - about the translateObject having to return an object, when using the lowest deps. it is using an older version of the component. Should we boost the requirement for the RoutingAuto component?

[dantleech]

Ignore last comment -- all the deprecations are fixed.

[wouterj]

this should also be merged into 1.1, I guess?

[dantleech]

I think so.

[dantleech]

Created issue #179

[stof]

tests pass in other envs, as the PHPUnit deprecation helper is set to weak.

@wouterj why is the helper set to weak for non-lowest deps ? This looks weird to me. I generally do the opposite (as lowest deps might end up triggering some deprecations by uisng a version of the deps before they stopped using the deprecated API of the other package)

[wouterj]

@stof I've improved it in the 1.1 branch: 724db6a The original config was from some months back: Lower versions didn't have any deprecations and the newer ones were having deprecations caused by third party bundles.