eugineerd

> I may want partial cloning to sync only specific types of components/ specific entity sets I can see how your proposed approach would be more general, however my main...

> In addition, my approach also handles the types without the Clone trait such as parent and child without modifications to the original components The proposed approach does not rely...

> ...here's what looks like needs to be done code-wise still to make this useful & robust in practice This is a solid plan of action as far as I...

> rather than short-circuit-failing when we find a component we can't clone, perhaps we should just accumulate and return the ComponentIds of components that couldn't be cloned This is certainty...

> Is this compared to the equivalent manual registration As far as I understand it, wasm-init works by exporting a bunch of symbols to final wasm and calling them from...

~~Managed to reduce wasm size considerably by removing closures from automatic type registration:~~ All sizes are in KB as reported by `du` on `reflection` example. | | wasm-release && wasm-bindgen...

Added a basic test for `no_auto_register`, there is also a doctest that should cover most of auto register functionality. > but can you also add some unit tests? What other...

Added support for platforms without inventory support (`auto-register-static` feature). The main caveats of the `static` approach are: 1. `load_type_registrations!` macro must be called before constructing `App` or using `TypeRegistry::register_derived_types`. 2....

> Does this mean that external users of the type registry (such as through the BRP registry schema endpoint) will receive no-longer-"valid" types? New types will only really be registered...