Rethinking the internal motion API to allow for interop with declarative libraries

[itsdouges]

Rethinking the internal motion API to allow for interop with declarative libraries

[itsdouges]

Ideally we want to not have an object be returned with multiple keys for different things. It feels confusing and just noisy. So with that said:

(elements, onFinish, renderChild) => React.ReactNode

(elements, onFinish, renderChild) => {
  return <Spring>{(style) => renderChild({ style }))}</Spring>
}

renderChild would be a HOF which already has style/className composing baked in. So we aren't actually calling the consumers render function - we're calling one supplied from the origin Motion component.

Not completely a fan of this yet. Need more ideas.

[itsdouges]

not going to support this.