New behavior of the IncludeInPage property

Discussion in English
1

Previously, the IncludeInPage and Visible properties could already be used together to prevent blinking.

InludeInPage={value: Show}
Visible={value: Show}

I don’t understand why you changed the IncludeInPage behavior.
Doesn’t this put extra load on the page?

Release DotVVM 5.0.0 major release · riganti/dotvvm

IncludeInPage no longer shows uninitialized content. When IncludeInPage={value: …} now evaluates to false on the server, it treats the controls as Knockout template resources (#2056). This eliminates the visibility of uninitialized content before JavaScript hides these controls.

2

Our goal was to ensure that there would be no flickering if you use just IncludeInPage={value: Show}. There should be no reason to use both of them.
I don’t have a benchmark for that, but I think it should be even faster. In DotVVM 4., when the page was loaded, Knockout had to take the contents of the element and create the template at runtime. With 5., the template is already there, and Knockout can just use it.

3

I loved the new features and updates that came with v5.

Great job and thanks!

However, instead of changing IncludeInPage, I wish you had added it as a new feature with a different name (e.g., IncludeInPageWithTemplate).