st-pipe not set before st-pagination

[brianchance]

For server side paging scenarios, st-pagination runs before st-pipe, leaving no rows. Switching st-pipe from a link to a pre-link seems to fix it...

                link: {
                    pre: function (scope, element, attrs, ctrl) {
                        if (ng.isFunction(scope.stPipe)) {
                            ctrl.preventPipeOnWatch();
                            ctrl.pipe = scope.stPipe.bind(ctrl, ctrl.tableState());
                        }
                    }
                }

I can then set the numberOfPages in the success callback...
tableState.pagination.numberOfPages = Math.ceil(data.totalItems / tableState.pagination.number);

[lorenzofox3]

Hello,

Not sure to understand exactly the issue, could you provide a plunkr ?

is this related to #146 ?

Thanks,

Laurent

[dmackerman]

Hmm, I think so. There's no way to determine the number of pages to show simply because the pipe doesn't get run on initial load.

[brianchance]

It is essentially the same issue. If you change stPipe to be a pre-link, it runs before stPagination so the initial call works.

As for a plunkr, just add an st-pagination to the pipe/ajax plugin, then remove the initial call to getAPage. It should not work, change stPage to a pre-link and it works. The numberOfPages can then be set in the callback (ala #146 or my sample above).

If you need me to I can create an actual plunkr.

Brian

[dmackerman]

Right. Changing it to a pre link works for me as well.

[lorenzofox3]

Ok thanks, took your fix !

[dmackerman]

Did this get released?

[lorenzofox3]

Yes fe73ca3