-
Notifications
You must be signed in to change notification settings - Fork 13
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
Remove cca dependency and implement compatibility for Symfony ^4.4 || ^5.1 #111
Remove cca dependency and implement compatibility for Symfony ^4.4 || ^5.1 #111
Conversation
Hotfix release 3.4.11 - Replace all key_exists with array_key_exists - Solve a problem with Contao 4.11 - Fix for the column field with hiden header - Add missing authors - Clean php code
@stefanheimes took a look at it - the MCW must also remain usable for Contao 4.4 and therefore the PR cannot be adopted as it is. However, the general problem is being worked on. |
This PR has no effect on it being usable in Contao 4.4. After merging this PR, a new minor version should be released. You can then still provide bugfixes for the previous minor version, if you ever need to (which is unlikely anyway, as Contao 4.4 is outdated anyway and only gets security fixes). |
I only do the "secretary job" - that's up to @stefanheimes |
Then may be @stefanheimes should join this discussion here 😁 |
Question @fritzmg: Why adding symfony/http-foundation or symfony/http-kernel as requirement. We didn't use them. So why adding more blocker to the list of requirements than needed? Why should I add all the sub requirements to the list, I'm only interested in the direct requirements and the result from them and not for the second or third sublevel requirement in the list. |
You are using these components here:
These are direct dependencies. Sure, both the Furthermore extensions broke because they did not properly require And similarly extensions broke because they did not properly require Especially the latter is a problem that is still present in many extensions today. So imho either you properly require all your actual dependencies, or you live with the fact that you might have to hotfix something, once one of these dependencies change in an incompatible way in newer versions (or if it gets dropped altogether). Also the fact that And these dependencies do not really block anything for Contao 4, as the switch to Symfony 6 will not happen for Contao 4. |
@fritzmg Thanks for the help. My problem was I had used the package name instead of the right Namespace for the search. So I totally missed this things. You are right it would be much better to add the requirements, so that we always have what we need. All looks okay, I think I will make a new 3.5. There are no API breaks, only the argument change for the events dispatcher :P |
Yes, this was changed in Symfony 4, with BC to the old Symfony 3 way. In order to be compatible with Symfony 4 and 5 though, only the new way works (event object as first argument, optional event name as second). But this does not break the MCW API. |
@fritzmg I have merged this PR into dev, which is the pre version for the 3.5.0. Can you test if everthing is working for you ? |
Everything seems to work fine as far as I tested 👍 |
@zonky2 @stefanheimes any chance to get this released as |
its @stefanheimes turn... |
Should be fine, but it was not merged correctly: https://github.com/menatwork/contao-multicolumnwizard-bundle/pull/114 |
Fixes #107
This also introduces proper Symfony dependencies and implements full compatibility with Symfony 4 and 5.