there were several discrepancies between the luau and ts types, which i addressed in this pull request:
fixed query.next returning a query object whereas it would be expected to return a tuple containing the entity and the corresponding component values
exported query.archetypes
made pair return a number instead of an entity, thus preventing direct usage of a pair as an entity while still allowing it to be used as a component. Additionally, introduced a type Id to act as the union of a pair and an entity - usage of Entity in component-like cases replaced with the aforementioned Id
exported components ChildOf, w, and Name
exported world.parent
wrecked indentation (not too rare around here....)
brief description of changes
there were several discrepancies between the luau and ts types, which i addressed in this pull request:
query.nextreturning a query object whereas it would be expected to return a tuple containing the entity and the corresponding component valuesquery.archetypespairreturn a number instead of an entity, thus preventing direct usage of a pair as an entity while still allowing it to be used as a component. Additionally, introduced a typeIdto act as the union of a pair and an entity - usage ofEntityin component-like cases replaced with the aforementionedIdChildOf,w, andNameworld.parentwrecked indentation(not too rare around here....)