-
-
Notifications
You must be signed in to change notification settings - Fork 344
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
Add support for SonataBlockBundle 4.x #1023
Conversation
Could you please rebase your PR and fix merge conflicts? |
403d342
to
9d9fd05
Compare
@wbloszyk try to follow same steps that the ones on my PR (modify construct) to have consistency here). |
9d9fd05
to
a3c3cd2
Compare
972404c
to
0d1a037
Compare
RTM |
@wbloszyk I need some explanation to understand this PR, Bundle sonataAdminORMAdmin could now use v.3 or v.4 of SonataBlockBundle. Maybe me logic is Bad, could you explain me plz ? |
@VincentLanglet ohhh okay didn't see my Bad thanks |
IMO the SonataAdminBundle PR should be merged first, because here we are not seeing the BlockBundle 4.0 installed yet: https://travis-ci.org/github/sonata-project/SonataDoctrineORMAdminBundle/jobs/709934612#L601 |
Could you please rebase your PR and fix merge conflicts? |
0d1a037
to
232d5ab
Compare
232d5ab
to
5429787
Compare
d186b7f
to
5a66b64
Compare
Update UPGRADE-3.x.md Co-authored-by: Grégoire Paris <[email protected]> Update UPGRADE-3.x.md Co-authored-by: Grégoire Paris <[email protected]>
4be9bec
to
b4a30b3
Compare
Thanks @wbloszyk ! |
Subject
I am targeting this branch, because this change have to be in 3.x - see sonata-project/SonataAdminBundle#6212.
Changelog