-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
prepend Twig form_themes config #444
Conversation
Does doing this allow to remove it from https://github.com/sonata-project/SonataPageBundle/blob/489e2fa48ce170b73e8bebc7ca9c10fac1d7778e/src/DependencyInjection/SonataPageExtension.php#L39 ? |
Yes, also it seems that the Page one can stop implementing the Prepend Interface Also for BC, it doesn't cause problems if both modules try to add the template For this MR, I think it could be done in the 1.x branch because it should be BC? |
It seems BC to me ; wdyt @jordisala1991 ? |
Also the part in the Documentation needs to be updated |
i think we could do, this in the 1.x branch because it should not be a BC break then PageBundle can require that version and remove their stuff. This would be a BC break for PageBundle because it doesn't need PrependExtensionInterface anymore |
It's better to do the doc changes in the same PR which is changing the behavior |
i removed the part from the Documentation about setup the twig config |
i just need to know if i should rebase it against 1.x branch or not |
To me yes. |
Thanks @Hanmac , after we deal with release of this pr, could you deal with the pagebundle code removal? |
Subject
I am targeting this branch, because is that BC or not?
Changelog
BC or not BC? or can this be done in 1.x too?
PageBundle does it too:
https://github.com/sonata-project/SonataPageBundle/blob/489e2fa48ce170b73e8bebc7ca9c10fac1d7778e/src/DependencyInjection/SonataPageExtension.php#L39