Description
I was updating the astro:transitions reference in docs (withastro/docs#12734) to add some undocumented APIs. Based on @martrapp feedbacks there, we might want to deprecate some APIs:
createAnimationScope()
isTransitionBeforePreparationEvent()
isTransitionBeforeSwapEvent()
TRANSITION_BEFORE_PREPARATION
TRANSITION_AFTER_PREPARATION
TRANSITION_BEFORE_SWAP
TRANSITION_AFTER_SWAP
TRANSITION_PAGE_LOAD
This seems reasonable to me. But, I'm not the framework expert here so let me know if there is any reasons not to do that. (ie., so far, I was thinking documenting everything (because some are used) except createAnimationScope()... if we don't want to deprecate createAnimationScope(), I need to know for docs)
I also noted that:
Not a big deal, but maybe we want to prevent that with a clean up similar to the one Florian has suggested for astro:actions in #14608 (comment)
Description
I was updating the
astro:transitionsreference in docs (withastro/docs#12734) to add some undocumented APIs. Based on @martrapp feedbacks there, we might want to deprecate some APIs:createAnimationScope()isTransitionBeforePreparationEvent()isTransitionBeforeSwapEvent()TRANSITION_BEFORE_PREPARATIONTRANSITION_AFTER_PREPARATIONTRANSITION_BEFORE_SWAPTRANSITION_AFTER_SWAPTRANSITION_PAGE_LOADThis seems reasonable to me. But, I'm not the framework expert here so let me know if there is any reasons not to do that. (ie., so far, I was thinking documenting everything (because some are used) except
createAnimationScope()... if we don't want to deprecatecreateAnimationScope(), I need to know for docs)I also noted that:
astro:transitionsare importable while those are internal typesastro:transitions/clientare importable while those are internal typesNot a big deal, but maybe we want to prevent that with a clean up similar to the one Florian has suggested for
astro:actionsin #14608 (comment)