Custom templates cause ExpressionChangedAfterItHasBeenCheckedException

[michaelbromley]

Custom templates cause ExpressionChangedAfterItHasBeenCheckedException

[michaelbromley]

Hi,

What version of this module are you using? The latest is beta.2 and is tested against angular2 beta.7.

Can you show me the code which yields this error?

btw, right now there is no simple way to make a Plunkr demo with this module (as far as I know) because it does not support systemjs. I plan to incorporate a systemjs-compatible build as soon as I get some time to do so.

[jayhahn]

Hi, this is the same issue as #12.

Custom Template doesn't work if you place the pagination-control before the actual ngFor elements. @michaelbromley I don't know how to create a plunkr but you can easily reproduce by checking out a quick angular2-seed project and then copy-pasting your example custom-template to it. Should be able to reproduce in few minutes.

[michaelbromley]

There is now a simple Plunker demo you can modify to try to reproduce the error. If you have time please replicate the error so I can investigate.

[CodeJason]

Hi,
Sorry for the long reply, been busy.
I've tried reproducing the issue on plunkr for a little while, but I can't seem to.
I've looked back in back in the project where I had the problem but I can't remember if it was a simple mistake or wrapping it in a ngIf.
Here's my custom template anyway, I added a service and tried other things but nothing fired the same error message. http://plnkr.co/edit/PFGn07aUISYnPPSU3ktb?p=preview
Thanks.

[michaelbromley]

Okay, I will close this issue then Feel free to re-open if you come across the error again.