EntityCommandBuffer Interface Question

I’ve noticed that in the EntityCommandBuffer struct there is an public API for:

EntityCommandBuffer.RemoveComponent<T>(Entity e)

but there isn’t one for:

EntityCommandBuffer.RemoveComponent(Entity e, ComponentType type)

The provided API calls an internal method which takes a ComponentType struct and the EntityManager class also provides a public API which takes a ComponentType struct. Wouldn’t it also make sense for the EntityCommandBuffer struct to offer a comparable API?

Definitely. The current API is not stable yet, and as we approach a more mature implementation, we will look at providing overloads and expose as much internal as we can.
I will take a note about this specific case, thanks for the input!

Awesome, that’s great to hear! :slight_smile: