About half of our resource controllers currently have some options for how the data can be sorted. Many of these are ordered at the db level, and a few at the Ruby level.
There is a modestly coherent system in place that manages these parameters, and they can be combined with filters and pagination.
Each sorting option currently has only one ordering supported. Some are ascending and others are descending, and most of them put nils at the end.
This task is to come up with a way that the sort order can be toggled by repeatedly selecting one of the sorting header links.
About half of our resource controllers currently have some options for how the data can be sorted. Many of these are ordered at the db level, and a few at the Ruby level.
There is a modestly coherent system in place that manages these parameters, and they can be combined with filters and pagination.
Each sorting option currently has only one ordering supported. Some are ascending and others are descending, and most of them put nils at the end.
This task is to come up with a way that the sort order can be toggled by repeatedly selecting one of the sorting header links.