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
Right now, we're deploying our contract suite through MUD's CLI, but it comes at the cost of automatically registering all methods in each Systems as World-functions.
While it is handy to have direct access to certain core methods by making direct calls to world, and because each modules are deployed on specific namespaces, the resulting function selectors registered corresponds to some concatenation of namespace and methodName
==> MySystem.foo().selector (deployned on namespace xyz) becomes xyz__foo().selector
I'd be in favour of registering our function suite manually so we can remove the xyz__ part, that way, function selectors will be an exact match of each system's interface, independantly of where those modules ends up being registered
The text was updated successfully, but these errors were encountered:
Right now, we're deploying our contract suite through MUD's CLI, but it comes at the cost of automatically registering all methods in each Systems as World-functions.
While it is handy to have direct access to certain core methods by making direct calls to
world
, and because each modules are deployed on specific namespaces, the resulting function selectors registered corresponds to some concatenation ofnamespace
andmethodName
==>
MySystem.foo().selector
(deployned on namespacexyz
) becomesxyz__foo().selector
I'd be in favour of registering our function suite manually so we can remove the
xyz__
part, that way, function selectors will be an exact match of each system's interface, independantly of where those modules ends up being registeredThe text was updated successfully, but these errors were encountered: