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 collection of files via running their respective
All files to be inlined are run in separate isolated VMs.
The merged response bodies are returned after inlining all files in the collection.
Note that before
.inline() returns the results, Boomla applies, some post
processing like namespacing CSS selectors and loading any Content-Security-Policy
rules (from .Trust files).
The location and statusCode fields of the response body are also merged respecting the following rules:
Simple example of 2 files returning hello world. Note that the response is wrapped in a div so that client-side tools can make it responsive.
Same example as above with all arguments specified.
Do not wrap children
Child throws an error.
Pass on head tags. Note that the response file is passed to collection.inline(), and so it is decorated with the head tags requested by the children. If you pass a different file instead of response, that file will be decorated instead.
Merge head tags for all.
If any child returns a status-code higher than that of the response file, the response file is updated.