The file to be inlined.
A collection of files to be inlined, in provided order.
Wrap each file in unique div to make client-side tools make them responsive.
Reference the context of the request - the page being visited. It defaults to the context file of the current transaction.
The request file that holds all input data, typically provided by the HTTP request, but may be modified by the callee, particularly for testing purposes. It defaults to the request file of the current transaction.
The response argument is a reference to the file that shall be decorated
with response metadata like
location or the
head string attribute.
It defaults to the response file of the current transaction.
Inline a file or collection via running their respective
All files to be inlined are run in separate isolated VMs.
When inlining a single file, its response body is returned. For collections, the merged response bodies for all files in the collection.
Note that after the response body is returned from the child transaction and before it is returned by this function, Boomla applies some post processing like namespacing CSS selectors and loading any Content-Security-Policy rules (from .ContentSecurityPolicy files).
The location and statusCode fields of the response body are also merged respecting the following rules:
Simple example of child returning hello world. Note that the response is wrapped in a div so that client-side tools can make it responsive.
Simple example of child returning hello world, this time with all arguments specified.
Do not wrap child.
Child throws an error.
Pass on head tags. Note that the response file is passed to os.inline(), and so it is decorated with the head tags requested by the child. If you pass a different file instead of response, that file will be decorated instead.
Merge head tags for all child transactions.
If the child returns a status-code higher than that of the response file, the response file is updated.