Vatroslav Vrbanic

Clean up + do TODO / fix TOFIX only issues things that cannot be moved to 1.0.0-next.X. If something cannot be resolved within an hour, create a new issue for...

to do or not to do?

... after closing #132

The `Empty` component is basically an `Object3D` / `Group` component. In the early stage of development I thought it was cool to name it like an "Empty" in blender, but...

Add shorthand prop `visible` to all components (where applicable)

1

Currently only via `props` attribute. Implementing this seems trivial, but it could affect interactivity logic / raycaster etc. leading to a bigger refactor. Basically, objects which are not visible are...

Currently the `SvelthreeAnimationFunctionReturn` type is being imported but is never used, nail it down.

Instance ( _`container`?_ ) injection needs to be nailed down / reconsidered. Currently related logic is being imported but is unused: `import { if$_instance_change } from "../logic/if$"` `import { ...,...

Instance ( _`orbitcontrols`?_ ) injection needs to be nailed down / reconsidered. Currently related logic is being imported but is unused: `import { if$_instance_change } from "../logic/if$"` `import { ...,...

e.g. is: `SVELTHREE > SvelthreeProps > unknown property 'color' in 'props' object -> not available on MeshNormalMaterial` should be: `SVELTHREE > SvelthreeProps > unknown property 'color' in '`**mat**`' object ->...

`SvelthreeGLTF.ts` + x : dynamically generated components are not being destroyed (at all? / properly?), reactive statements bound to `$svelthreeStores[sti]` cause errors

1

e.g. in the `Mesh` component: https://github.com/vatro/svelthree/blob/d98605278ec144997a1632ccc61b5c3bac8fd3f6/src/components/Mesh.svelte#L785 I've stumbled upon this when changing test-scenes (_pages_) in the SvelteKit test-app. The error was thrown only when switching from the `gltf-to-comp-1` test-scene to...