Jakob Hellermann

I pushed the update in https://github.com/jakobhellermann/bevy_editor_pls/pull/34

The panic seems to happen when doing something like ```rust world.resource_scope(|res: Mut, world| { world.insert_resource(Resource::default()); }); ``` but I'm not sure on which resource. The panic message could really use...

The crate is now released as `0.1.0` for bevy `0.8` :tada:

I think the reflection API isn't quite enough yet, because it only allows calling `add_component` with a `&dyn Reflect`, and there is no way to just insert the default value.

The problem with that trick is that there is no way to find out if `DynamicStruct` or `DynamicTupleStruct` (or `DynamicEnum` in the future) are the correct ones to use just...

I opened a PR for `#[reflect(Default)]`: https://github.com/bevyengine/bevy/pull/3733

I don't know if we can rely on the `FromWorld` bound always being on a component, I believe it was only added as a necessity as there is no other...

Also I finished up and pushed the code for an `Add` menu that lets you spawn new bundles into the world: It doesn't use reflection and will only work for...

Yeah I think the DynamicStruct workaround is definitely worth merging and a good solution until bevy supports something else

The gizmo crate uses bevy_mod_picking while this crate uses bevy_mod_raycast, which the picking crate is built on. I don't know how flexible bevy_mod_picking and the gizmo crate is and I...