Alexander Nanberg

Added a failing test for this #154, trying to fix the actual issue too but having some problems understanding TS AST and where to put the fix 😓

>three-addons seems easier to read but I wonder if it's worth the complication of publishing multiple packages... Not worth it imo, and it makes it too easy for consumers to...

@mattrossman > Silly question, but isn't this already possible with the existing three/examples/jsm pattern? Yeah, although I think `three/addons` is much more user friendly than `three/examples/jsm`. Especially when used with...

Any update on this? It would make everything so much cleaner!

I'm using a schema but this seems to work quite well ```ts const schema: Schema = { avatar: { in: ['body'], isURL: true, optional: { options: { nullable: true }...

Isn't the return type something like `[number, number, number, string]`? Or does the `offset` arg break that?

IMO this doesn’t belong in the lib and is not worth the extra complexity, particularly since you easily can fix this on the consumer side

An alternative approach could be to throw an error (with a good description) if multiple calls to `init` occurs. The part I'm not a super big fan of is that...

@deniszatsepin Did you ever solve it? I'm facing a similar issue. I have 2 dynamic bodies that do make contact but the callback is never fired. A bit unrelated but...

> contact report for a world is better and actually you can write your own emit to dispatch events in the contact callback for the individual bodies. Fair point! >...