Pagination: allow setting of a custom css class on <li>

[SylTi]

Make possible <li class="btn btn-primary"> for example

[codecov-io]

Current coverage is 85.62% (diff: 100%)

Merging #1115 into development will not change coverage

@@           development      #1115   diff @@
=============================================
  Files               35         35          
  Lines             1280       1280          
  Methods            228        228          
  Messages             0          0          
  Branches           213        213          
=============================================
  Hits              1096       1096          
  Misses             184        184          
  Partials             0          0          

Powered by Codecov. Last update ec6ccc3...d1a3852

[valorkin]

need to think about it a sec,

1. classLi property doesn't describe what it does
2. class="{{ classLi }} " need to check will it work with[class]="classLi"`

[SylTi]

1. I can change the name to something li;e setLiClass if you want (I'm open to suggestions).
2. [class] overwrite all existing class. That's not what we want

[valorkin]

1. by meaning it seems to be pageBtnClass ? seems to be pretty intuitive name
2. what about [ngClass] ?

[SylTi]

1. Fine by me I will change it to that and push the new commit.
2. It won't work for the pager already have : [ngClass]="{'pull-right': align}"

[valorkin]

what I am afraid of: if pageBtnClass will change after disable changed, it can overwrite the whole class

[SylTi]

By setting the property to `btn btn-primary' :

https://postimg.org/image/e5s4zkz2x/

Disable seems to work fine.

[valorkin]

yes, now it looks much more readable,
if you are in hurry I can merge and publish it is as @beta now and cover with tests later
or you can cover it with test now

[SylTi]

I will try to do the tests this weekend !

[SylTi]

Is there no existing test for the pagination ? Can't find the .spec