Indeed, queries will not look into the component’s internal state, which is also not their goal.
Depending on your game setup and what you try to achieve, there are multiple ways to achieve this. For example:
- If you really need the game ID to be stored in a component
like %Game{id: "game_id_1"}
This is not an ideal case if you have multiple parallel games and you need to query one of them. Still, you can achieve it by querying all Game components with their Entitites, then find the one you are looking for. For example:
{entity, game_component} =
Ecspanse.Query.select({Ecspanse.Entity, Game})
|> Ecspanse.Query.stream()
|> Enum.to_list()
|> Enum.filter(fn {entity, game_component} -> game_component.id == "game_id_1" end)
Now you have your game entity, and game_component, if you need it.
- If you do not need to store your game ID in a component
You can optimize your code by spawning your game entity with a custom ID. You can still pass the Game component to it if you want.
Ecspanse.Command.spawn_entity!(
{
Ecspanse.Entity,
id: "game_id_1",
components: [{Game, id: "game_id_1"}]
# Then you can query the entity by its ID
{:ok, game_entity} = Ecspanse.Query.fetch_entity("game_id_1")
# Then if you need, you can fetch the game component for the game entity
{:ok, game_component} = Game.fetch(game_entity)
I hope this solves your current issue.
