[Paginator] Add functionality to jump to first and last page

[Chris2011]

Bug, feature request, or proposal:

Feature request

What is the expected behavior?

There should be 2 buttons like << and >> to jump to the first and last page.

What is the current behavior?

There is no button for this. There is only a button for < and > prev and next.

Items per page: 10 - 1 - 10 of 100 < >

What is the use-case or motivation for changing an existing behavior?

If you have a long list, often it is needed to jump to the end and back to the first page/first items.

Items per page: 10 - 1 - 10 of 100 << < > >>

Is there anything else we should know?

#7615 - as a reference.

[lharries]

Hi @andrewseguin I'd be keen to give this one a go

[andrewseguin]

Sounds good to me, let's set the requirements and iterate from there:

• Needs to be optional (turned on through some Input())
• Should be able to draw up some icons that match the material icon (can't use the icons directly, should be done with divs): https://material.io/icons/#ic_first_page and https://material.io/icons/#ic_last_page
• Needs tests
• Needs to be added as an example in documentation

[lharries]

I agree with the above requirements.

For tests would it just be the spec tests? I don't see the paginator in the e2e tests.

[andrewseguin]

Yup just some spec unit tests would suffice, try to consider the main case and edge cases, e.g. the jump-to-first button should be disabled when on the first page

[lharries]

Whilst doing the above I found two bugs in the spec file. Would it be best to do them as separate PRs or in the same PR that I'm currently working on, when I have completed this feature?

1. A test was wrongly named. See fix here
2. There was an off-by-one error where the index of the last page was wrongly calculated.
   This happened in both the goToLastPage() method and in the following test 'should disable navigating to the next page if at last page'. See fix here
   In headless chrome, it was going to page index 10 to check that it could no longer navigate forward. Whilst there are 10 pages they are starting from index 0 and therefore the last page is in fact index 9.

The bug fix for 2 is required in order to write a valid test for the current feature.

[andrewseguin]

Good catch - if you submit the fixes via separate PRs, that'd be a lot easier for us.

[lharries]

Thanks! And will do

[lharries]

Do I need to create issues for them or straight to the PRs?

[andrewseguin]

No issue needed, just a PR will do