-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
AdminLTE 3 implementation #5989
Conversation
Could you please rebase your PR and fix merge conflicts? |
composer.json
Outdated
"knplabs/knp-menu": "^2.0 || ^3.1", | ||
"knplabs/knp-menu-bundle": "^2.3 || ^3.0", | ||
"sonata-project/block-bundle": "^3.18.3 || ^4.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why these changes ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is draft. I need it for working demo for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is draft. I need it for working demo for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, sorry for the too early review. 😅
I think this will need an upgrade note for the user. If he made some custom page, override, etc. He'll be happy to know which class to use instead of the previous one. Something like, |
I think refer for adminlte and bootstrap upgrade will be enought. |
@@ -0,0 +1,14 @@ | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have to commit all the admin-lte files ?
Can't we declare the dependency in the composer.json or something ?
Could we use https://packagist.org/packages/almasaeed2010/adminlte ?
Unfortunaly the AdminLTE release notes doesnt help a lot https://github.com/ColorlibHQ/AdminLTE/releases And I didn't found the reason for your changes in https://getbootstrap.com/docs/4.0/migration/#stable-changes Something more precise than
Into
What about adding a line in the upgrade note like
And if we makes some others class changes, adding a note for it. |
You can find adminlte upgrade guide here: https://adminlte.io/docs/3.0/upgrade-guide.html I waiting for webpack. At first i will end "Drop SonataCoreBundle" PRs. At second "add support for BlockBundle 4.0. Then i will end this PR. BTW If adminlte and bootstrap upgrade guide is not clear enought i can add own upgrade notes. |
Could you please rebase your PR and fix merge conflicts? |
Could you please rebase your PR and fix merge conflicts? |
Could you please rebase your PR and fix merge conflicts? |
Could you please rebase your PR and fix merge conflicts? |
What with #6147 ?? If x-editable will be drop then I can finish this PR. |
IMHO #5461 this should be finish first, having to review 200k lines PR because we don't have assets correctly installed with npm is super hard and keep adding them makes that other PR harder and harder |
I dont want psuh assets but is require for tests. BTW I will finish wecore too. |
@greg0ire Can you merge 3.x branch to master in AdminBundle? |
I'm happy to help with implementing these upgrades defined in the upgrade guide of Admin LTE3. As I can see the implementation is still incomplete. For instance admin LTE3 requires font-awesome5 which uses 'fas' instead of 'fa' when using icons. Is it possible to ignore the webpack-encore update for now so we can get the theme implemented correctly. Others can help with this if we can get some of your code merged. If you want you can focus on 'Drop SonataCoreBundle' but my opinion is that we should not create a lot of dependencies between pull requests. Could you fix the conflicts? Or is something else blocking this from merging ? |
The problem for now is x-editable not support bootstrap 4. |
Ok thanks for your response. At the moment i'm not using x-editable and are using a custom theme. So hard to say if we should hold the release for this feature. We might be able to build something like this in combination with Popper.js which is part of admin lte 3 but it's hard to get it to work in way x-editable did with all those field types. But if the goal is using bootstrap 4 and admin lte3 my advice is to disable x-editable for now so other can help with finding a replacement or further implement this theme. |
There is an issue for this #6147 |
This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Subject
You can check result here:
http://demo.wbloszyk.pl
I am targeting this branch, because it is BC-break.
Closes #5597
Changelog
To do
Update - 07.07.2020
Current assets system have many dependencies to other Sonata bundles (like
sonatacore
files). It mean it is not simple to upgrade vendors and templates. It is possible to do it at once at major update but require upgrade all sonata bundles at once. To avoid it and allow upgradesonata 3
tosonata 4
one by one bundle this thigs will be do: