Currently if a null appears in a table column, for instance in data returned by postgres, sorting on that gives an arbitrary order. This is due to null being neither greater or less than any string, which makes the sort unstable. Change the table sort function to compare on nullness first. Note this is a slight behaviour change for numbers, which would otherwise treat null and 0 as equivalent. Signed-off-by: Martin Packman <gzlist@googlemail.com>
Name |
Last commit
|
Last Update |
---|---|---|
.. | ||
__snapshots__ | Loading commit data... | |
ColorPalette.jest.tsx | Loading commit data... | |
PasswordStrength.jest.tsx | Loading commit data... | |
backend_srv_specs.ts | Loading commit data... | |
datemath.jest.ts | Loading commit data... | |
emitter.jest.ts | Loading commit data... | |
file_export.jest.ts | Loading commit data... | |
flatten.jest.ts | Loading commit data... | |
kbn.jest.ts | Loading commit data... | |
location_util.jest.ts | Loading commit data... | |
manage_dashboards.jest.ts | Loading commit data... | |
org_switcher.jest.ts | Loading commit data... | |
rangeutil.jest.ts | Loading commit data... | |
search.jest.ts | Loading commit data... | |
search_results.jest.ts | Loading commit data... | |
search_srv.jest.ts | Loading commit data... | |
store.jest.ts | Loading commit data... | |
table_model.jest.ts | Loading commit data... | |
ticks.jest.ts | Loading commit data... | |
time_series.jest.ts | Loading commit data... | |
value_select_dropdown.jest.ts | Loading commit data... |