Skip to content

[7.2 only] fix(common): properly check NaN value#30023

Closed
trotyl wants to merge 1 commit intoangular:7.2.xfrom
trotyl:async-nan-7.2
Closed

[7.2 only] fix(common): properly check NaN value#30023
trotyl wants to merge 1 commit intoangular:7.2.xfrom
trotyl:async-nan-7.2

Conversation

@trotyl
Copy link
Copy Markdown
Contributor

@trotyl trotyl commented Apr 22, 2019

closes #15721

Change for 7.2.x branch of #22305 per #22305 (comment)

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Issue Number: #15721

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@trotyl trotyl requested a review from a team April 22, 2019 07:39
@benlesh benlesh added the area: common Issues related to APIs in the @angular/common package label Apr 22, 2019
@ngbot ngbot bot added this to the needsTriage milestone Apr 22, 2019
@trotyl
Copy link
Copy Markdown
Contributor Author

trotyl commented Jun 1, 2019

Stale.

@trotyl trotyl closed this Jun 1, 2019
@angular-automatic-lock-bot
Copy link
Copy Markdown

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 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area: common Issues related to APIs in the @angular/common package cla: yes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants