Skip to content

test(paginator): fix incorrect test name #9584

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 25, 2018

Conversation

lharries
Copy link
Contributor

the test was referencing the wrong page

discovered in #9278

the test was referencing the wrong page

discovered in angular#9278
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 25, 2018
lharries pushed a commit to lharries/material2 that referenced this pull request Jan 25, 2018
Whilst there are 10 pages they are starting from index 0 and therefore the last page is in fact index 9.
This error was repeated both in the length calculation and in the assertion statements, therefore the
test passed when it should have failed.

Discovered in angular#9584 and a required fix to implement the first/last buttons correctly
@andrewseguin andrewseguin added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 25, 2018
@jelbourn jelbourn merged commit 6c766cf into angular:master Jan 25, 2018
@jelbourn jelbourn added target: patch This PR is targeted for the next patch release and removed target: patch This PR is targeted for the next patch release labels Jan 29, 2018
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants