fix(cdk-stepper): coercing selectedIndex value to a Number

[s2-abdo]

Expected Behavior📗

The label of the stepper should show the current step index

Actual Behavior 📕

The number shown is wrong. It's adding a '1' for some reason

Description

Make a simple implementation of a Multi-Stepper and found out that the label information in the mobile view is not showing properly whenever 'selectedIndex' is used. It is handling the value as a string, therefore the result is 11/3 for example instead of 2/3.
'1' + 1 will be handled as a string concatenation.

Steps to Reproduce 🔬

Code
<mat-horizontal-stepper [linear]="true" selectedIndex="1"> <mat-step label="One"></mat-step> <mat-step label="Two"></mat-step> <mat-step label="Three"></mat-step> </mat-horizontal-stepper>

Proposed solution

Add a coercing to Number type for the selectedIndex value in its setter.

[crisbeto]

The code looks good, but can you add a unit test for it?

[ngbot]

Hi @s2-abdo! This PR has merge conflicts due to recent upstream merges.
Please help to unblock it by resolving these conflicts. Thanks!

[crisbeto]

LGTM

[crisbeto]

@s2-abdo the CI failures will be fixed by #14854.

[ngbot]

I see that you just added the pr: merge ready label, but the following checks are still failing:
     status "ci/circleci: api_golden_checks" is failing
     status "ci/circleci: bazel_build_test" is failing
     status "ci/circleci: tests_local_browsers" is failing
     status "branch-manager" is failing
     status "ci/circleci: tests_browserstack" is failing
     status "ci/circleci: tests_saucelabs" is failing

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

[mmalerba]

@s2-abdo looks like that rebase wasn't quite right

[josephperrott]

Removing merge ready label as the PR needs to be rebased back to master and then the cla can be checked again.

[mmalerba]

@s2-abdo I attempted to fix this, I think it looks like how you had it: master...mmalerba:pr/14817 I can push to your PR branch if you like

[s2-abdo]

@s2-abdo I attempted to fix this, I think it looks like how you had it: master...mmalerba:pr/14817 I can push to your PR branch if you like

@mmalerba sure, be free to do that. 👍

[googlebot]

CLAs look good, thanks!

[angular-automatic-lock-bot]

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.}