Entity.Has does not work after World.Create( <object array> )

[Mathetis]

Hi, I'm curious if the following behavior is by design, if I am misusing it, or if this is a bug.

I have a use case where the array of components arrived as an object[], which contains references to struct components (boxing isn't problematic for my case here). I want to create an entity from those components. Here's a simple example:

struct SomeComponent { ... }

object[] components = new object[] { new SomeComponent() { ... } };

Entity entity = world.Create(components);

bool hasComponent = entity.Has<SomeComponent>();  // <-- this will be false.

Interestingly, the Entity contains the component with the correct type when viewed in a debugger, including with correct state. However, the Entity does not report that it has the component.

I'm curious if something is happening with typing and casting internally, however, the debugger does show the correct type.

I am able to work around this by retrieving the types (e.g. (ComponentType)(x.GetType()) ) and creating a ComponentType[] array, using that to create an archetype, and then setting each component (using only the object reference). This is not a big deal to me as I'll be putting this logic in a service object anyway, but I'm curious if this is intended.

[genaray]

@Mathetis Hey there and thanks! :)

Well... You are using that correctly and it should work. May i ask which version you are using? It might be a bug, however the latest beta/preview version (1.2.3.4-beta) had some improvements and the issue might be gone :)

[Mathetis]

Thanks for the quick reply! I'm using 1.2.3. I looked at the Arch code and it wasn't obvious why it wasn't working yet. I can definitely give the beta a try. This library looks really useful and I appreciate the compositional simplicity that makes it far easier to include in a project.

[genaray]

Thanks a lot! :) Lemme know if the beta works, if not ill convert this to an issue to fix the bug

[genaray]

Just looked at this, this is actually intended behavior rn.
The generic overloads are favored in such a case since there's no world.Create(object[]) overload... there's however : world.Create(Span<ComponentType> or world.Create(ComponentType[]); which can be used to create the entity. After this you can set the components from an object[] array like this : entity.SetRange(object[]); :)

I will add a world.Create(object[]) in the future

[Mathetis]

Understood, thanks for confirming.