Skip to content

Conversation

@hrocha16
Copy link
Contributor

@hrocha16 hrocha16 commented Feb 9, 2019

Fixes #13477

@alan-agius4
Copy link
Collaborator

alan-agius4 commented Feb 11, 2019

Kindly squash your commits into a single one and maybe use the suggest warning?

Thanks.

@hrocha16
Copy link
Contributor Author

Thanks!

@alan-agius4 alan-agius4 added the target: patch This PR is targeted for the next patch release label Feb 12, 2019
@alan-agius4
Copy link
Collaborator

@filipesilva PTAL

@filipesilva
Copy link
Contributor

LGTM, thanks for taking this on @hrocha16!

@alexeagle alexeagle merged commit b611e7f into angular:master Feb 13, 2019
@liorwohl
Copy link

liorwohl commented Apr 3, 2019

Hi, is there a way to hide the warning? I dont even use zone.js (its an Angular Element) but I get this warning anyway.
Thanks

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

Labels

target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No warning given when using ES2017

6 participants