forcePage prop is not respected

Greetings good people maintaining this pagination lib.

From your docs on forcePage

To override selected page with parent prop. Use this if you want to control the page from your app state.

But this is not true. If forcePage={5} , for example, and you click on on page 1, page 1 becomes active instead of 5. I see from your tests

• it('(observation) is not totally controlled when forcePage is provided', () => {
• it('(observation) is not totally controlled when forcePage is provided, even when it is 0', () => {

that this is somewhat desirable, but not sure why?

If component is controlled, it should stay that way, there’s no point having forcePage if it won’t control the component, it behaves the same as initialPage

[fila90]

Great!! One more question, can you bring back support for IE in v9? Somehow it got lost in v8 but we need to support IE 11 in our app, since it’s not a super complex lib, it would be nice if we could use the latest version 😄

[MonsieurV]

Yes, for the PR, fork, then from your repo branch you can submit a PR.

I let the ticket open just to remind me to finalize the v9 release, but yes indeed, this won’t be an issue anymore when we have a truly fully-controlling page prop.