Calling the addObject function with a directory path doesn't seem to do anything at all - custom object modules are not required.
It looks like all this function does is add the provided path to newObjects in main.lua, but newObjects is only ever visted when main.lua is first evaluated (i.e. when the module is required, before the addObject function can even be called).
To Reproduce
Steps to reproduce the behavior:
Add a custom object module to a folder that has a debug print or something at the top
Pass the folder to basalt.addObject("...") in a test program
Run the program and observe that the custom modules are not imported
Expected behavior
The custom object modules would be imported and registered as object types in Basalt.
Describe the bug
Calling the
addObjectfunction with a directory path doesn't seem to do anything at all - custom object modules are not required.It looks like all this function does is add the provided path to
newObjectsinmain.lua, butnewObjectsis only ever visted whenmain.luais first evaluated (i.e. when the module isrequired, before theaddObjectfunction can even be called).To Reproduce
Steps to reproduce the behavior:
basalt.addObject("...")in a test programExpected behavior
The custom object modules would be imported and registered as object types in Basalt.
Checklist