You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we can't find out if we are introing or outroing from a "transition generator" (that's what I'm calling the functions that are returned from transition functions -- the ones that are called just before a transition starts to get a TransitionConfig object).
While we can use separate in: and out: directives (like for crossfade), for a number of use cases that's unneeded boilerplate.
I propose that we start passing an intro: boolean to them:
This wouldn't be a breaking change, but it would expand on the contract we have to support in the future. Personally, I think it's worth it, being such a small change, but what are our thoughts on it?
I tried coming up with hacky ways to figure out if it's an intro but came up with nothing that worked reliably.
The text was updated successfully, but these errors were encountered:
Currently, we can't find out if we are introing or outroing from a "transition generator" (that's what I'm calling the functions that are returned from transition functions -- the ones that are called just before a transition starts to get a
TransitionConfig
object).While we can use separate
in:
andout:
directives (like forcrossfade
), for a number of use cases that's unneeded boilerplate.I propose that we start passing an
intro: boolean
to them:This wouldn't be a breaking change, but it would expand on the contract we have to support in the future. Personally, I think it's worth it, being such a small change, but what are our thoughts on it?
I tried coming up with hacky ways to figure out if it's an intro but came up with nothing that worked reliably.
The text was updated successfully, but these errors were encountered: