Dynamic value for datepicker min breaks component

[calebegg]

Clicking on dates does nothing in this example:

https://stackblitz.com/edit/angular-4ywmkp?file=src/app/datepicker-min-max-example.ts

[crisbeto]

It's because you're returning a new date object on every change detection which causes Angular to run an infinite change detection loop. It should work if you put the value into a property instead.

[calebegg]

This used to work up until about a month ago.

How can I diagnose this kind of issue in the future? Normally when there's an infinite change detection loop there's some sort of console logging in dev mode, right?

[crisbeto]

I'm guessing that it may have started as a result of #19973 which marks related components for check when the inputs change. We've had other reports about this, but decided not to fix it because we'd only be hiding your performance issue from you (see #19907). Closing as a duplicate of #19907.

[angular-automatic-lock-bot]

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.}