PipelineOptions
Read-only settings that affect different behaviors of a Pipeline.
Parameters
whether the rendering stage should produce pretty output code
whether the rendered code should be wrapped in a template code. For example, an HTML wrapper may add <html><head>...</head><body>...</body></html>, with the actual content injected in body
the starting directory to use when resolving relative paths from function calls
whether media storage should be enabled. If enabled, media objects referenced in the document are copied to the output directory and those elements that use them (e.g. images) automatically reference the new local path. This doesn't take effect with the base Markdown flavor, as the media architecture is defined by Quarkdown through a com.quarkdown.core.context.hooks.MediaStorerHook. If this is disabled, MediaStorageOptions are ignored.
rules that override the default behavior of the media storage system
the error handler strategy to use when an error occurs in the pipeline, during the processing of a Quarkdown file
port to communicate with the local server on. If not set, no server communication is performed. In a practical scenario, this is injected into JavaScript to communicate with the server, for example to enable dynamic reloading.