When called from a macro loaded from a local macro repository, a jar in the class path or via the WarpFleet™ resolver, this function accesses the value of a configuration key present in the Warp 10™ configuration.
This allows to define macro properties outside of the macro itself, which proves very handy when exposing macros via WarpFleet™ for example.
The typical use case would be a macro which needs a token to interact with Warp 10™, the token can be set in the configuration file.
The configuration keys looked up are those built by adding
@ and the macro name to the key specified as parameter to
MACROCONFIG will check if the keys exists, if not it will remove the part of the macro name after the last
/ and will try that new key. It will successively try all names up to the last part of the macro name.
If none of those keys existed, the call will end in error.
So for example, if
MACROCONFIG is called from a macro
my/test/macro to retrieve the value associated with
mykey, it will look up the following keys in the configuration:
mykey@my/test/macro mykey@my/test mykey@my