'listItemsPerPageShow' doesn't work well inside template HTML

[joadtor]

Hi, I've set the tasty as follows:

Controller:

var myTheme = {
          iconUp: 'fa fa-sort-amount-asc',
          iconDown: 'fa fa-sort-amount-desc',
          listItemsPerPage: [10, 20, 50, 100],
          itemsPerPage: 10,
          loadOnInit: true
        };

HTML (View):

<div tasty-table bind-resource-callback="vm.getResource" bind-filters="vm.filterBy" bind-theme="vm.ppqTheme" bind-init="vm.init">
...
   <div tasty-pagination bind-template-url="vm.paginationTemplate"></div>
...
</div>

HTML (Template):

...
<div class="col-xs-3 text-left">
    <div class="btn-group">
      <button type="button" class="btn btn-default" 
      ng-repeat="count in listItemsPerPageShow" 
      ng-class="classPaginationCount(count)" 
      ng-click="page.setCount(count)" ng-bind="count"></button>
    </div>
  </div>
...

Resulting just in 2 buttons ( only for '10' and '20') instead of 4. If I change the value this way: listItemsPerPage: [5, 10, 20, 100], I get 3 buttons ( '5' , '10', '20').

I can fix it forcing ng-repeat to use my own list (ng-repeat="count in [10,20,50,100]"), but i guess it's not an intended behaviour.

Thanks

[Zizzamia]

Simple question, how many rows do you have?
If you have listItemsPerPage: [5, 10, 20, 100] and 15 rows you just need the 3 buttons ( '5' , '10', '20').
Instead if you have 50 rows you need the fourth one for 100.

[joadtor]

Now that you mention it, I just tried with 11 rows. Testing with more values (about 120) leads me to the situation that you've described. It would be interesting to be able to disable that behaviour from the options.