-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Upgrade the project to Symfony 4.0 then to Symfony 4.2 #50
Comments
…ings during the tests, making them fail. It's also a first step toward removing deprecation warning in order to update the project to Symfony 4.0
There is no more deprecation warnings when running the project so we could be able to transition to 4.0 easily |
Saw another interesting thing: we can show Symfony deprecation in unit tests, could you look at the official documentation? |
We already show them but there is no deprecation anymore. After some testing I realized that we can't upgrade to 4.0 since Mink only support Symfony 2 and 3. From this we have two obvious solutions :
We might also try this : https://blog.rafalmuszynski.pl/how-to-configure-behat-with-symfony-4/ |
The server has been upgraded in a new branch but there is thing we still need to do :
|
I merged the branch on |
…generate a phpunit.xml file when first executing the script or when this file is missing.
I think we should separate the todo list in several issues, this one is too big |
Closing this issue since all the remaining work has been exported to separated issues. |
Context
The differences between Symfony 3.4 and Symfony 4.0 are minor. The deprecated methods in 3.4 just desapear in 4.0 but otherwise the features are the same.
Then we should probably upgrade to 4.2 which is the next LTS version.
The faster we upgrade the project, the lesser code will need to be updated.
Todo
The text was updated successfully, but these errors were encountered: