The Content-Type for encoding a specific property.
Default value depends on the property type: for string with format being binary – application/octet-stream; for
other primitive types – text/plain; for object - application/json; for array – the default is defined based on
the inner type. The value can be a specific media type (e.g. application/json), a wildcard media type
(e.g. image/*), or a comma-separated list of the two types.
A map allowing additional information to be provided as headers, for
example Content-Disposition.
Content-Type is described separately and SHALL be ignored in this section. This property SHALL be ignored if the
request body media type is not a multipart.
Describes how a specific property value will be serialized depending on its type.
See Parameter Object for details on the style property. The behavior follows the same values as query parameters,
including default values. This property SHALL be ignored if the request body media type is not
application/x-www-form-urlencoded.
When this is true, property values of type array or object generate separate parameters for each value of the
array, or key-value-pair of the map.
For other types of properties this property has no effect. When style is form, the default value is true. For all
other styles, the default value is false. This property SHALL be ignored if the request body media type is not
application/x-www-form-urlencoded.
Determines whether the parameter value SHOULD allow reserved characters, as defined by RFC3986 :/?#@!$&'()*+,;=
to be included without percent-encoding.
The default value is false. This property SHALL be ignored if the request body media type is not
application/x-www-form-urlencoded.
Returns the relative, descendent directory path between this module and other.
Throws if no such path exists.
For example, if module mod1 has path /dir1/mod1.pkl, and module mod2 has path /dir1/dir2/dir3/mod2.pkl,
then mod1.relativePathTo(mod2) will return List("dir2", "dir3").
A common use case is to compute the directory path between a template located at the root of a hierarchy
(say rootModule.pkl) and the currently evaluated module (accessible via the module keyword):
The output of this module.