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
I want to create my own module resolver to allow people to import different application objects. So do I have to use the export table or the module.Context property to make it available for importing from other scripts?
The text was updated successfully, but these errors were encountered:
You do not need to use Context.Module directly because of it is just one of context values uses for some internal purposes. But available for public access because of why not.
The central object of improt/export mechanism is ExportTable, but it has no public setter (there are some reasons for this).
Simple way to do this is create a module with "application objects" defined in its Context, then write (or generate) a script with lines like "export Forms; export Web; Export BlaBla;". One per each defined object. After this you can return this module as result of TryGetModule.
Also see this.
I want to create my own module resolver to allow people to import different application objects. So do I have to use the export table or the module.Context property to make it available for importing from other scripts?
The text was updated successfully, but these errors were encountered: