This is valid only for query parameters and allows sending a parameter with an empty value. Default value is
false. If style is used, and if behavior is n/a (cannot be serialized), the value of allowEmptyValue SHALL be
ignored. Use of this property is NOT RECOMMENDED, as it is likely to be removed in a later revision.
When this is true, parameter 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 parameters this property has no effect. When style is form, the default value is true. For all
other styles, the default value is false.
Example of the parameter's potential value. The example SHOULD match the specified schema and encoding properties
if present.
The example field is mutually exclusive of the examples field. Furthermore, if referencing a schema that contains
an example, the example value SHALL override the example provided by the schema. To represent examples of media
types that cannot naturally be represented in JSON or YAML, a string value can contain the example with escaping
where necessary.
Each example SHOULD contain a value in the correct format as specified in the parameter encoding. The examples
field is mutually exclusive of the example field. Furthermore, if referencing a schema that contains an example,
the examples value SHALL override the example provided by the schema.
If in is "path", the name field MUST correspond to a template expression occurring within the path field in the
Paths Object. See Path Templating for further information.
If in is "header" and the name field is "Accept", "Content-Type" or "Authorization", the parameter definition
SHALL be ignored.
For all other cases, the name corresponds to the parameter name used by the in property.
Determines whether the parameter value SHOULD allow reserved characters, as defined by RFC3986 :/?#@!$&'()*+,;=
to be included without percent-encoding.
This property only applies to parameters with an in value of query. The default value is false.
If the parameter location is "path", this property is REQUIRED and its value MUST be true. Otherwise, the property
MAY be included and its default value is false.
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.