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
Some methods within a module, directives, blocks, or events, require access to other module's configuration variables. The way Amethyst currently behaves is that it whitelists a couple of core events and directives, blocking any other modules from accessing everything. For blocks, this isn't an issue, since blocks have to get access to the entire config object if they are supposed to conditionally perform the contents inside, which may be from other modules.
The default should be the module's own configuration object, but it should be an option that the module developer can set. Maybe set each directive entry inside directives to be either a plain function (configuration object is the local module's), or an object with options, one of which being the function to execute, say callback.
The text was updated successfully, but these errors were encountered:
Some methods within a module, directives, blocks, or events, require access to other module's configuration variables. The way Amethyst currently behaves is that it whitelists a couple of core events and directives, blocking any other modules from accessing everything. For blocks, this isn't an issue, since blocks have to get access to the entire config object if they are supposed to conditionally perform the contents inside, which may be from other modules.
The default should be the module's own configuration object, but it should be an option that the module developer can set. Maybe set each directive entry inside
directives
to be either a plain function (configuration object is the local module's), or an object with options, one of which being the function to execute, saycallback
.The text was updated successfully, but these errors were encountered: