Make world:contains() return a boolean instead of an entity which may or may not exist
Impact of your Changes
Developers can now use another two methods without casting the objects to have them
Doesn't alter performance, although alters behavior if someone expects world:contains() to return an entity (impossibly unlikely, especially since the method itself was never exposed in types)
Brief Description of your Changes.
world:contains()
inWorld
typequery:drain()
inQuery
typeworld:contains()
return aboolean
instead of an entity which may or may not existImpact of your Changes
Developers can now use another two methods without casting the objects to have them Doesn't alter performance, although alters behavior if someone expects
world:contains()
to return an entity (impossibly unlikely, especially since the method itself was never exposed in types)Tests Performed
Run tests and implement as directed
Additional Comments
N/A