Job detail page

Fixed key sorting. Turns out reverse() doesn't sort keys in reverse, it just reverses them. To sort in reverse: sort().reverse(). Ugh. Fixed JS liting issues for dashboard stuff.
This commit is contained in:
Chris Houseknecht
2014-07-02 12:43:31 -04:00
parent 7e45143fa1
commit cebc1d6030
3 changed files with 11 additions and 11 deletions

View File

@@ -947,7 +947,7 @@ function($rootScope, $log, UpdatePlayStatus, UpdateHostStatus, AddHostResult, Ge
newKeys = [], newKeys = [],
plays = JSON.parse(JSON.stringify(scope.jobData.plays)), plays = JSON.parse(JSON.stringify(scope.jobData.plays)),
keys = Object.keys(plays); keys = Object.keys(plays);
keys.reverse(); keys.sort().reverse();
for (idx=0; idx < scope.playsMaxRows && idx < keys.length; idx++) { for (idx=0; idx < scope.playsMaxRows && idx < keys.length; idx++) {
newKeys.push(keys[idx]); newKeys.push(keys[idx]);
} }
@@ -973,7 +973,7 @@ function($rootScope, $log, UpdatePlayStatus, UpdateHostStatus, AddHostResult, Ge
if (scope.activePlay) { if (scope.activePlay) {
tasks = JSON.parse(JSON.stringify(scope.jobData.plays[scope.activePlay].tasks)); tasks = JSON.parse(JSON.stringify(scope.jobData.plays[scope.activePlay].tasks));
keys = Object.keys(tasks); keys = Object.keys(tasks);
keys.reverse(); keys.sort().reverse();
newKeys = []; newKeys = [];
for (idx=0; result.length < scope.tasksMaxRows && idx < keys.length; idx++) { for (idx=0; result.length < scope.tasksMaxRows && idx < keys.length; idx++) {
newKeys.push(keys[idx]); newKeys.push(keys[idx]);