You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If the source file defining a vat fails to export a buildRootObject function, the error message the kernel prints is vat source bundle lacks (default) setup() function, which is confusing
To Reproduce
PIck a vat. Rename buildRootObject to buildRootOrbject. Run.
Expected behavior
I'd expect an error message more like vat source bundle lacks a buildRootObject() function
The text was updated successfully, but these errors were encountered:
, and that code is factored to handle both export function buildRootObject() -style vats and the older export default function setup() style. The presence of a named buildRootObject export should override any default. We have a managerOption flag to enable the use of setup, which is disabled for everything except the comms vat. The particular sequence there is:
look for buildRootObject, use it if present
else grab default
complain if it's not a function
complain if the use of setup is not enabled in the vat options
else use it
Maybe that should be refactored to be more like:
look for buildRootObject, use it if present
if setup is disabled, complain about the lack of `buildRootObject
Describe the bug
If the source file defining a vat fails to export a
buildRootObject
function, the error message the kernel prints isvat source bundle lacks (default) setup() function
, which is confusingTo Reproduce
PIck a vat. Rename
buildRootObject
tobuildRootOrbject
. Run.Expected behavior
I'd expect an error message more like
vat source bundle lacks a buildRootObject() function
The text was updated successfully, but these errors were encountered: