Upgrading to Vue 3: breaking changes to named slots?

Upgrading to Vue 3: breaking changes to named slots? vue slot Slots are mighty, but they are not almighty For example, slot content does not have access to the state in the child component vue default slot Vue iOS MD ion-button expand=block>Blockion-button> Content is placed between the named slots if provided without a slot end

vue default slot Slot components can declare their own props, these props are then accepted at the top level FormulateInput and passed to the appropriate slot component as a

vue3 slot Simplify the use of scoped slots with the new v-slot syntax introduced in 0 beta 3  slot, and override the footer completely via the modal-footer slot Note vueTarget, property, A reference to the modal's Vue VM instance componentId