How to migrate 0.3 dgrid event.results passed by dgrid-refresh-complete?

[twelveeighty]

In the 0.3 days of dgrid, a dgrid-refresh-complete event had a 'results' property with the latest data on the grid. We relied on this property to run post-processing against the results (totals, etc.) with having to re-query the storage back-end. In version 0.4, this 'results' property has been removed.

What would be the "new" way of post-processing results returned from a Rest dstore upon dgrid-refresh-complete? In our case, the dgrid is hooked directly to the Rest dstore because I want to have sorting handled by the rest server. I also don't want to query the rest server twice, once for the grid and once more for post-processing.

Edit: how about if the method set("collection", some_collection) returns the promise from refresh() that gets called by set("collection")?

[kfranqueiro]

To be honest, I'm not certain that the removal of the results property was 100% intentional. Its initial removal from OnDemandList traces to a commit in March 2014 which was likely while some parts of dstore were still in flux.

I'm kind of curious though what kind of post-processing you're performing, in terms of whether there's a better answer to your question.

[twelveeighty]

I'm all for alternatives if that's a better design! Here's what we were using the event.results property for: we query a rest server for a sales order type dataset. This dataset returns a low number of rows, less than 20. On the UI side, we have a page that shows the sales order dataset in a dgrid. In the v0.3 days, when the grid is populated using set("store"), we calculate the total of the sales order using the event.results returned as part of the dgrid-refresh-complete event. This was very efficient, since the rest server is only queried once for a given sales order.
We need sorting of the dataset to be handled by the rest backend, which is exactly what dgrid is doing if we set the rest store/collection directly on the grid.

In essence, we are using the set("collection") in the same way as refresh() would work, but I don't want to call refresh() again since set("collection") has already pulled all the data I need. That's why I suggested to make set("collection") return a promise just refresh() does?

I'm open to suggestions. Currently, as a work-around, I have extended OnDemandGrid as follows:

var CachedOnDemandGrid = declare([ OnDemandGrid ], {
    _cachedResults: null,
    renderQueryResults: function(results, beforeNode, options) {
        this._cachedResults = results;
        return this.inherited(arguments);
    },
    _getCachedResults: function() {
        return this._cachedResults;
    },
});
[...]
var MyGrid = declare([ CachedOnDemandGrid, ... ]);
var grid = new MyGrid({ ... });
var store = new Rest({
    idProperty: 'someId',
    sortParam: "orderBy",
    target: '/some/url/'
});
grid.set("collection", store.filter({someId: 3}));
grid.on("dgrid-refresh-complete", function(event) {
    var results = event.grid.get("cachedResults");
    results.forEach(function(entry) {
        ...
    }); 
});

This works, but it's a bit of a hack, since I'm relying on renderQueryResults() being called somewhere deep inside the set("collection") calls.