-
Notifications
You must be signed in to change notification settings - Fork 298
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
Refresh AdminLTE to 2.3.2 #104
Conversation
Just executed script -> didnt test
Glad it's useful for you. Is there a particular reason you want to update to 2.3.2? I'm reluctant to update it without a lot of testing. Unfortunately, right now the testing is pretty much a manual process, checking all the examples in the documentation. |
Well, I already done that job of testing and I found no issues. Everything worked fine for me (rendering, functionality). |
add really big dashboard covering about 70-80% of all elements used or described. update news file as I believe version update to AdminLTE 2.3.2 is fine and not going to break anything.
cc @wch Any update on this ? |
add news and update descripition.
Hi @wch , Thank you very much. |
I just remembered that there were a number of changes that needed to be done manually to AdminLTE to make it work properly with shinydashboard. See: The code changes are in this branch: It's a little tricky to update AdminLTE, because we don't want to reintroduce those issues. It might be that most efficient way to deal with this is to for me to update AdminLTE myself and reapply the changes. Hopefully AdminLTE hasn't changed too much, and the commits on that branch can be re-applied to the AdminLTE 2.3.2 branch. Regarding tests: it's not clear to me exactly how the tests in In R, the automatic package check process sources files in the |
In https://github.com/rstudio/shinydashboard/blob/master/inst/AdminLTE/README-shiny-mods.md
From brief look, it seems to me to be fixed :: https://github.com/almasaeed2010/AdminLTE/blob/master/dist/js/app.js#L536-L549
Was that an issue before ? Because I could not tell the difference. But will need to look at it later. |
But, this is reproducible for me indeed: #42. I am not a javascript guru, but maybe if you could a look on https://github.com/almasaeed2010/AdminLTE/blob/master/dist/js/app.js#L557-L589 and tell if its now fixed by them ? (seems rather not) At this stage, 2 out of 4 things are fixed as I believe. One is font thing, another one must be fixed. This sounds pretty good I think |
I was doing the same upgrade locally and I don't think #42 has been fixed by them as a user reported that bug after my update to 2.3.2 which led me to discover #42. I'm not sure where the collapse/expand events are listened to by shiny though, couldn't find the source listening to that event in the shiny library. |
Most probably not. Thus I also assume #42 is really not fixed. |
@wch @chrisirhc Ok, now have commited the changes and the bug in #42 is fixed for me. This means Winston can only explain one thing (the fonts) and otherwise it is ready to be merged. 👏 Edit: Ping: @wch Maybe should I squash commits ? |
@dmpe Sorry, been busy with a lot of family and work things in the last couple months. It's a little challenging to assess some of these changes, but I'll give some feedback now. |
@@ -1,6 +1,6 @@ | |||
Package: shinydashboard | |||
Title: Create Dashboards with 'Shiny' | |||
Version: 0.5.1 | |||
Version: 0.5.2 |
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.
Please use 0.5.1.9000.
@dmpe, it looks pretty good overall - thanks for your attention to detail! Here's my setup, for some context for the comments.
|
It would be helpful to have comments in the manual tests just what the manual test is looking for (if it's a specific issue). |
delete `interactive()` because tests are in Rignore add comments fix tabItems issue comment repro issues fix version, bump both package further ahead and make sure that rstudio#42 is not repro on my pc
@@ -1,6 +1,4 @@ | |||
This branch of AdminLTE contains the following changes from the stock version, to make it work better with Shiny. | |||
|
|||
* Attached collapse click event handler to document, instead of to each collapse button. This is the same fix as https://github.com/almasaeed2010/AdminLTE/pull/304; if that is merged, then it should be possible to go to the stock version. Also see https://github.com/rstudio/shinydashboard/issues/17 for a test app. | |||
* The box collapse function triggers 'shown' and 'hidden' events, so that Shiny knows when outputs are visible or not. See https://github.com/rstudio/shinydashboard/issues/42 for a test app. |
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.
#42 not repro on my PC, (to delete)
@@ -0,0 +1,190 @@ | |||
library(shiny) |
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.
This example is way too complicated -- I'd hold off adding it until there's a minimal example, and when we understand what the problem actually is. In general, I'd like to minimize the number of additional changes in this pull request.
Thanks Wiston for quick action on this again. At least, for (European) today I am done as i have turned off my Ubuntu VM where i do all the programming stuff. You can either merge now or (European) tomorrow I would delete the #117 example from repository. I would also add some more comments as I have left some of them. And down-bump version of libraries. |
and delete 117 test.
Hi @wch
Firstly, I like this package very much !! Thank you for it. Also, this will be a very important package for me in the near future and I will try to contribute to it.
This PR updates AdminLTE 2.1.2 from to 2.3.2 with changelog here: https://github.com/almasaeed2010/AdminLTE/releases. Yes, there were some additions, and they will need to be checked somehow (BTW: how do you test it ?).
Please, comment & I will try to fix it.
Thanks.