Bug fix - when using ng-grid's sort capabilities, there's an inner map that maps between the original index of an item to its new index after the sort.
 The item that's indexed at place 0 after the sort, might get a wrong index from this map, due to a bug of 'a = x || y' in which x is evaluated as false when it's 0, even though 0 is in fact a valid index.