Jason Ye

The remaining issue with the diffing algo should be addressed by a combination of the Fragment VNodes work and ~~https://github.com/salesforce/lwc/pull/3042/commits/b9cfd81e4bfbdf19612456460d0e90322ac25ce2~~ https://github.com/salesforce/lwc/pull/3047. That PR uses the new Fragment VNodes to mark...

https://github.com/salesforce/lwc/pull/3047 is now ready to merge and should address the issues with the diffing algo by making use of the VFragments work.

/nucleus test

cc @jmsjtu if-else work just merged! 🎉

@Templarian I noticed this attribute is missing from the stubs packaged with our internal lightning components repo; do we need to update it there too?

Thank you for contributing this update.

Stubs are generated elsewhere and copied here. Changes will be updated in the supporting package.

@nolanlawson Yes, that's correct. I've added that detail to the main description.

The following fallback behavior should be removed when we're ready to fully remove `"any"`: https://github.com/salesforce/lwc/pull/3972

@jodarove Here are the main changes I had in mind: https://github.com/salesforce/lwc/pull/3405 is the main one I think addresses our diffing concerns. https://github.com/salesforce/lwc/pull/3140 dealt with an issue with native slotting