-
Notifications
You must be signed in to change notification settings - Fork 74
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 bower support #440
base: master
Are you sure you want to change the base?
Add bower support #440
Conversation
Conflicts: adagios/bi/templates/business_process_standalone.html adagios/bi/templates/business_process_view.html adagios/media/css/import_contrib.css adagios/objectbrowser/templates/list_object_types.html adagios/status/templates/base_status.html adagios/status/templates/status_detail.html adagios/status/templates/status_index.html adagios/templates/base.html
Conflicts: adagios/contrib/lib/dashboards/raymii.html adagios/templates/base.html
If bower.json is the same as in savoirfairelinux/adagios, the rest will follow :) |
@matthieucan Yes it is :) |
This pull request seems to have some issues. I think the main issue is that there are javascript libarary updates within this pull request. One problem noted is that the objectbrowser (Configure) list table does not render at all. Might have something to do with datatables being upgraded to 1.10.2. Adagios versions
This needs some more testing before we can merge. We cannot update each library in independant pull requests since the libraries have versioned dependencies into each other and will not work without updating the others. |
@matthieucan I hope you can REhelp me with this one |
@titilambert does it work when you downgrade datatables? |
We need a test for object browser.configure... It seems to be one of the
|
@matthieucan In fact, it's only DT_bootstrap which is missing... Thanks ! |
|
@tomas-edwardsson I think I resolve the issue with the last commit |
This patch is making me uncomfortably aware of how many (shaky?) javascript dependencies we have. Does anyone have opinion on the dependencies that are outside bower repositories (like select2 which points to a github repository). There is a real risk, that 1 or 2 years in the future those links might be gone, effectively breaking adagios. A workaround could be to fork those repositories and point our links there. |
@palli keep in mind most bower repos are github repos! |
yes, which helps us partly if (when) any of them updates and breaks backwards compatibility, but not if the projects are removed or renamed. |
Sure, the idea of forking them is nice, and doesn't prevent to still linking to the original repos :) |
I don't think this is a real issue and we should cross that bridge when we need to. The libraries that we are using are packaged in the rpm/deb packages so if any of them are removed/disappear we can find the source there. I really want to avoid having to maintain forks if it is not needed. |
Are you still working on this patch ? I noticed a few issues that might block this patch from getting into master, namely:
Going forward, i'm pretty sure we need something like bower to keep our javascript dependencies maintainable, but maybe this was to big of a change in one point in time. Also I think it is a general problem that we don't have a copy of them locally as well. I propose the following:
This way when doing git clone of adagios, we are guaranteed to have a working version of adagios because a downloaded copy of the dependencies exists in media/external Comments ? |
Hello ! Do you want I close this issue ? |
Hello !
Here the bower support for Adagios :)
@matthieucan Do you see any error ?
Thanks !