Rename legacy notification so it's less confusing

Signed-off-by: Joas Schilling <coding@schilljs.com>
This commit is contained in:
Joas Schilling 2018-01-17 14:55:48 +01:00
parent 4b50fe7560
commit 52f8d75d1a
No known key found for this signature in database
GPG key ID: 7076EA9751AACDDA
2 changed files with 2 additions and 2 deletions

View file

@ -11,7 +11,7 @@
*/ */
/** /**
* this gets only loaded if an update is available and then shows a temporary notification * This only gets loaded if an update is available and the notifications app is not enabled for the user.
*/ */
$(document).ready(function(){ $(document).ready(function(){
var text = t('core', '{version} is available. Get more information on how to update.', {version: oc_updateState.updateVersion}), var text = t('core', '{version} is available. Get more information on how to update.', {version: oc_updateState.updateVersion}),

View file

@ -63,7 +63,7 @@ class Application extends App {
} }
if ($updateChecker->getUpdateState() !== []) { if ($updateChecker->getUpdateState() !== []) {
Util::addScript('updatenotification', 'notification'); Util::addScript('updatenotification', 'legacy-notification');
\OC_Hook::connect('\OCP\Config', 'js', $updateChecker, 'populateJavaScriptVariables'); \OC_Hook::connect('\OCP\Config', 'js', $updateChecker, 'populateJavaScriptVariables');
} }
} }