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

ERROR Error: ExpressionChangedAfterItHasBeenCheckedError: #8

Open
easyworks opened this issue Jun 22, 2018 · 1 comment
Open

ERROR Error: ExpressionChangedAfterItHasBeenCheckedError: #8

easyworks opened this issue Jun 22, 2018 · 1 comment

Comments

@easyworks
Copy link

Hello!
I am coming again, and brought a bad news!
An error occurred during use today:

ERROR Error: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: '@fadeinout: undefined'. Current value: '@fadeinout: true'. It seems like the view has been created after its parent and its children have been dirty checked. Has it been created in a change detection hook ?

Is it a new bug?
My test environment is angular@5.2.11 and chrome@66.0.3359.181

@easyworks
Copy link
Author

Looking forward to your reply!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant