ScopeContext
A context that is the result of a fork from an original parent Context. Several properties are inherited from it.
Parameters
context this scope was forked from
Properties
The pipeline this context is attached to, if it exists. A context can have up to 1 attached pipeline.
Mutable information about the final document that is being created.
External libraries that can be loaded by the user into libraries. These libraries are, for instance, fetched from the library directory (--libs
option) and can be loaded via the .include {name}
function.
Tables that store key-value localization pairs for each supported locale. Each table is identified by a unique name.
Media storage that contains all the media files that are referenced within the document. For example, if an image node references a local image file "image.png", the local file needs to be exported to the output directory in order for a browser to look it up. This storage is used to keep track of all the media files that may need to be exported.
Global properties that affect several behaviors and that can be altered through function calls.
Functions
Returns a copy of the queue containing registered function calls and clears the original one.
If no matching function is found among this ScopeContext's own libraries, parent's libraries are scanned.
Loads a loadable library by name and registers it in the context. After a successful load, the library is removed from loadableLibraries and added to libraries, with its Library.onLoad action executed.
Localizes a key from the stdlib table.
Localizes a key from a table.
Performs an action locking the enqueuing of function calls. This causes register to do nothing until the action is completed. Any function call enqueued during the action is discarded and won't be expanded by the pipeline.
Registers a new LinkDefinition, which can be later looked up via resolve to produce a concrete link from a reference.
Enqueues a function call to the parent's queue if it is a MutableContext, or to this context otherwise. This lets the registration go up the context tree so that it can be expanded from the root context in the next stage of the pipeline.
Tries to resolve a reference link to an actual link. If the resolution succeeds, ReferenceLink.onResolve callbacks are executed.