docs(components/cdk/scrolling): add note about view recycling with dy…

[michaelsanford]

…namic components

Added a clearer note about the behaviour of view recycling in cdk-virtual-scroll-viewport
containers when rendering dynamic components.

Fixes #15838

[Santalov]

Hello, can you clarify that statement a bit, please? Really need it.

What exactly the state preservation means? Does it mens that in this code location binding will never change?

<cdk-virtual-scroll-viewport
        [itemSize]="itemSize"
        [minBufferPx]="itemSize * 2"
        [maxBufferPx]="itemSize * 4"
>
        <div
          *cdkVirtualFor="let location of locations"
          [style.height]="itemSize + 'px'"
        >
          <app-location-card
            [location]="location"
          >
          </app-location-card>
        </div>
</cdk-virtual-scroll-viewport>

[michaelsanford]

What exactly the state preservation means?

The behaviour is discussed n the linked issue which this PR closes, with examples.

Are you suggesting the change to the documentation is not clear enough and could be improved?

[andrewseguin]

Thanks for adding to the docs. Based on your initial issue it looks like a lot of people would benefit from this sort of messaging. However, I don't think "dynamic components" will be clear enough. Is there another way to describe what users should watch out for in more Angular-ish terms? Should users specifically be careful about components not calling their constructor or ngOnInit when reused?

[devversion]

Hey, please re-open the pull request if still valid. The PR got auto-closed by GitHub when we renamed our primary branch.

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