Kris Baumgarter

Here is a naive attempt at implementing a Motion component for the sake of conversation: https://codesandbox.io/s/eager-monad-kqnyl?file=/src/App.js I wasn't sure how to set a rest state dynamically when useSpring requires default...

I do think we should be careful to separate two concerns. One is more hooks and declarative methods for building animated interactions to match the ease of use and coverage...

This came up again. In other cases I tried using useSprings, which while it is less convenient is technically correct. However, when using useTransition not having the ability to set...

This was the closest I could come up with: https://codesandbox.io/s/dynamically-update-compoundbody-v2-4k93f?file=/src/App.js Note the rotation issues will be fixed with the latest PR.

I realized I was putting the type in the wrong place. I moved it to the hook and out of the worker.

I support this change as well.

Thanks so much for all your hard work Cody. I wanted to add here some type exports for the different r3f props which were previously exported as `Vector3`, `Color`, etc.

> Hello! Whats the status of V9? I'm looking to use the lifecycle stages in `useUpdate` but it looks like its not officially ready yet. Hey! So we have been...

Good question. I just checked. `primitive` still has `applyProps` called before it has a parent but something about the logic is different and the object is still added to `interactions`....

That's a good catch. And yeah that makes sense about the children being dynamic. I think traversing up is the best solution so that portaling is respected.