Skip to content
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

fix(core): updating ngZone error message #20182

Closed
wants to merge 1 commit into from
Closed

fix(core): updating ngZone error message #20182

wants to merge 1 commit into from

Conversation

willmendesneto
Copy link
Contributor

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
[x] Other... Please describe: typo fix on Zone.js error

What is the current behavior?

screen shot 2017-11-04 at 7 28 56 pm

Issue Number: N/A

What is the new behavior?

Using polyfill instead prolyfill

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@willmendesneto willmendesneto changed the title chore(ngZone): updating Zone.js error message fix(ngZone): updating Zone.js error message Nov 4, 2017
@willmendesneto willmendesneto changed the title fix(ngZone): updating Zone.js error message fix(core): updating ngZone error message Nov 4, 2017
@trotyl
Copy link
Contributor

trotyl commented Nov 4, 2017

Duplicate of #20121.

PS: prolyfill is the right word.

@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 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants