bump rails-timeago

Here we also set autoDispose to false. This is an option that was introduced
sometime after our last bump. Default is true and it disposes timeago object
if it is not in DOM. But that is the way we initialize timeago objects, therefore
if we have autoDispose=true then they will be disposed before they inserted in DOM.
So by using autoDispose=false we enforce previous behavior that worked fine for us.
This commit is contained in:
cmrd Senya 2017-04-10 18:26:39 +03:00 committed by Steffen van Bergerem
parent a880de28a8
commit 87ed561d45
No known key found for this signature in database
GPG key ID: 315C9787D548DC6B
3 changed files with 6 additions and 4 deletions

View file

@ -183,8 +183,8 @@ gem "typhoeus", "1.1.2"
gem "gon", "6.1.0"
gem "hamlit", "2.8.0"
gem "mobile-fu", "1.3.1"
gem "rails-timeago", "2.16.0"
gem "will_paginate", "3.1.5"
gem "rails-timeago", "2.11.0"
# Logging

View file

@ -568,7 +568,7 @@ GEM
rails-i18n (4.0.8)
i18n (~> 0.7)
railties (~> 4.0)
rails-timeago (2.11.0)
rails-timeago (2.16.0)
actionpack (>= 3.1)
activesupport (>= 3.1)
rails_admin (0.8.1)
@ -734,7 +734,7 @@ GEM
unf (~> 0.1.0)
typhoeus (1.1.2)
ethon (>= 0.9.0)
tzinfo (1.2.2)
tzinfo (1.2.3)
thread_safe (~> 0.1)
uglifier (3.1.2)
execjs (>= 0.3.0, < 3)
@ -886,7 +886,7 @@ DEPENDENCIES
rails-assets-markdown-it-sup (= 1.0.0)!
rails-assets-perfect-scrollbar (= 0.6.16)!
rails-i18n (= 4.0.8)
rails-timeago (= 2.11.0)
rails-timeago (= 2.16.0)
rails_admin (= 0.8.1)
rb-fsevent (= 0.9.8)
rb-inotify (= 0.9.8)

View file

@ -26,6 +26,8 @@
}
});
}
$.timeago.settings.autoDispose = false;
});
};
})();