reading `LuaControl.force` should only return `LuaForce`, not `LuaForce | string`

[aSemy]

At the moment, reading LuaControl.force returns either a string or LuaForce, but it should only return a LuaForce.

  const player = game.players[playerIndex]

  const force : LuaForce = player.force
  // ERROR 
  // TS2322: Type 'ForceIdentification' is not assignable to type 'LuaForce'. 
  // Type 'string' is not assignable to type 'LuaForce'.

However, assigning a string should be possible.

I think this is probably true anywhere that ForceIdentification can be read, but that's a guess. At a minimum it's also documented as the case for

• LuaControl.force
• LuaEntity.render_to_forces
• BaseEntity.render_to_forces

I also guess this is similar to #7

This is a really minor issue, it's not disrupting me, it's just something I noticed.

https://lua-api.factorio.com/latest/LuaControl.html#LuaControl.force

The force of this entity. Reading will always give a LuaForce, but it is possible to assign either string or LuaForce to this attribute to change the force.

[GlassBricks]

Hi, thanks for the suggestion!

I verified that reading ForceIdentification always yields a LuaForce. A similar thing is true for ItemPrototypeSpecification and TechnologyIdentification.

This change was easy enough to implement, so I did just that.

Released in v0.18.1

[aSemy]

Thanks for the quick fix! It's really nice using this library.