Swiper loop mode synchronization during dynamic addSlide updates

Loop Mode and Dynamic Content

The loop: true configuration in Swiper.js creates internal clone elements to facilitate infinite scrolling. When slides are added at runtime using the addSlide() method, the library must recalculate these clones and synchronize the internal index mapping to maintain visual continuity.

Cloning Constraints

When the loopSlides property is explicitly defined, there is uncertainty regarding whether the buffer automatically scales to accommodate the new DOM structure. If the total slide count changes significantly after initialization, the duplicated elements may not align with the updated slide set, potentially causing blank spaces or jitter during touch transitions.

What is the precise sequence of methods required to ensure loop clones are fully re-synchronized after calling addSlide()? Does the loopSlides value require a manual update to prevent the buffer from losing track of the actual slide count?