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

ExpressionChangedAfterItHasBeenCheckedError: using fxHide #421

Closed
dhuallanca opened this issue Sep 14, 2017 · 11 comments
Closed

ExpressionChangedAfterItHasBeenCheckedError: using fxHide #421

dhuallanca opened this issue Sep 14, 2017 · 11 comments
Labels
needs: demo P4 Low-priority issue that needs to be resolved

Comments

@dhuallanca
Copy link

Expression has changed after it was checked. Previous value: 'false'. Current value: 'true'

I am using fxHide.gt-sm

@ThomasBurleson
Copy link
Contributor

Please provide a Plunkr demo.

@ThomasBurleson ThomasBurleson added this to the v2.0.0-Beta.11 milestone Sep 14, 2017
@ThomasBurleson
Copy link
Contributor

Related to #415

@nadjem
Copy link

nadjem commented Sep 20, 2017

Had same issue and fix it after reading this blog post

@ThomasBurleson
Copy link
Contributor

@nadjem - There are several solution approaches... I am curious how you fixed it on your version.

Maxim's blog article Everything you need to know about the 'ExpressionChangedAfterItHasBeenCheckedError' error is a great article.

@nadjem
Copy link

nadjem commented Sep 20, 2017

@ThomasBurleson
In my case, I have two components that communicate together via a service and I added the "setTimeout" in both. Like this example from the article

ngOnInit() {
       setTimeout(() => {
           this.parent.text = 'updated text';
       });
   }

and it work for me. ;)

@ThomasBurleson
Copy link
Contributor

ThomasBurleson commented Sep 20, 2017

@nadjem - Understood. In our case, a setTimeout() outside the ObservableMedia seems like a bandaid that simply hides the infection.

@nadjem
Copy link

nadjem commented Sep 20, 2017

@ThomasBurleson ok I understand, if you have a better solution i am really interested

@mackelito
Copy link

I have the same issue but non fxFlex related.. the problem occurs when using md-accordion component from Material Design. I want to have the panel expanded on load if the route match "outerLinkActive #rla="routerLinkActive" [expanded]="rla.isActive"" this works but gives this error in the console.

I can solve this problem by using "changeDetection: ChangeDetectionStrategy.OnPush" but then I cant use outerLinkActive... still looking for a solution :)

@mackelito
Copy link

This is a race condition present in the RouterLinkActive.
angular/components#6701
angular/angular#18983

@ThomasBurleson ThomasBurleson added the P4 Low-priority issue that needs to be resolved label Nov 29, 2017
@CaerusKaru
Copy link
Member

It's been three months since a demo was requested. If you can provide one with the specified behavior, we can reopen this issue.

@CaerusKaru CaerusKaru removed this from the v5.0.0-rc.1 milestone Jan 15, 2018
@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 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs: demo P4 Low-priority issue that needs to be resolved
Projects
None yet
Development

No branches or pull requests

5 participants