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 arise when use ngFor to render <nz-timeline-item> #66

Closed
SangKa opened this issue Aug 17, 2017 · 1 comment
Labels

Comments

@SangKa
Copy link
Contributor

SangKa commented Aug 17, 2017

I'm submitting a...


[x] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Support request => Please do not submit support request here

Current behavior

Sample Code:

import {Component, OnInit} from '@angular/core';
@Component({
  selector: 'nz-demo-timeline-basic',
  template: `
    <nz-timeline>
      <nz-timeline-item *ngFor="let event of events">{{event}}</nz-timeline-item>
    </nz-timeline>`,
  styles: []
})

export class NzDemoTimelineBasicComponent implements OnInit {

  events = [
    'Create a services site 2015-09-01',
    'Solve initial network problems 2015-09-01',
    'Technical testing 2015-09-01',
    'Network problems being solved 2015-09-01'
  ];

  constructor() {
  }

  ngOnInit() {
  }
}

Error Screenshot:
image

Expected behavior

In the real world, the timeline events data should almost come from the backend rather than the hardcode. So the NzTimelineComponent should support for dynamic render.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment


Angular version: 4.3.4

ng-zorro-antd version: 0.5.0-rc.0

Browser:
- [x] Chrome (desktop) version 59
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX
 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

@lock
Copy link

lock bot commented Feb 19, 2019

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants