Closed dbu closed 4 years ago
@acrobat wdyt ? only problem i have is that i get mismatches on the @expectedDeprecation
with a %A
in the expectation. do you have an idea what happens here? if not, i tend to just drop those expectations, we do see the depreactions currently work and they will be removed in the next major anyways...
@alexander-schranz can you try this branch in sulu and report if you run into any issues? are you using the bundle as well, or only the component? the bundle likely also needs some adjustments.
@dbu Looks good! If you apply this diff, the expectedDeprecations work again (there was a (backtick).
missing at the end! The %A
is indeed confusing but it has nothing to do with the error itself, dunno why it's displayed 🤷♂️
Diff: https://gist.github.com/acrobat/c929ad46a84a91d1f51f18755e6dd85c
@dbu looks good from the sulu side. Did not get any error and the routing did work.
We are also using the Bundle I used the symfony-5
branch there to test it.
I think the travis build got "lost" during the maintenance this morning. Can you restart a new build in the travis interface?
triggered a manual build: https://travis-ci.org/github/symfony-cmf/Routing/builds/677716799 (that will not update the PR here, but if its green, i guess i will merge)
do you have any inputs on the code @acrobat or does it all look good?
oh, actually travis-ci is very clever and did update us here. and even better, its green
triggered a manual build: https://travis-ci.org/github/symfony-cmf/Routing/builds/677716799 (that will not update the PR here, but if its green, i guess i will merge)
do you have any inputs on the code @acrobat or does it all look good?
The code looks good to me! 🚢
Continuation of the work by @acrobat
I realized that the VersatileRouterInterface is used to provide meaningful debug messages when something did not work, and i think for that its worth to keep it. So i only deprecated the
supports
method. And adjusted the debug message method to handle the new mode as well.