Explicitly setting an order_by fixes the issue of workflow nodes coming back out of whack on page 2 and beyond

This commit is contained in:
Michael Abashian
2017-02-13 19:02:10 -05:00
parent 3f0c42c1f6
commit 0e6e116fa3

View File

@@ -49,7 +49,7 @@ export default {
// flashing as rest data comes in. Provides the list of workflow nodes // flashing as rest data comes in. Provides the list of workflow nodes
workflowNodes: ['workflowData', 'Rest', '$q', function(workflowData, Rest, $q) { workflowNodes: ['workflowData', 'Rest', '$q', function(workflowData, Rest, $q) {
var defer = $q.defer(); var defer = $q.defer();
Rest.setUrl(workflowData.related.workflow_nodes); Rest.setUrl(workflowData.related.workflow_nodes + '?order_by=id');
Rest.get() Rest.get()
.success(function(data) { .success(function(data) {
if(data.next) { if(data.next) {