This string MUST be the semantic version number of the OpenAPI Specification version that the OpenAPI document
uses.
The openapi field SHOULD be used by tooling specifications and clients to interpret the OpenAPI document. This is
not related to the API info.version string. The default value corresponds to the version of the spec we've
implemented in this package.
Since this library specifically follows version 3.0.3 of the OpenAPI spec, this value cannot change unless this
library is updated to implement a later version.
Contains relative paths to an individual endpoint. The field name MUST begin with a forward slash (/). The path is
appended (no relative URL resolution) to the expanded URL from the Server Object's url field in order to construct
the full URL. Path templating is allowed.
When matching URLs, concrete (non-templated) paths would be matched before their templated counterparts.
Templated paths with the same hierarchy but different templated names MUST NOT exist as they are identical.
In case of ambiguous matching, it's up to the tooling to decide which one to use.
A declaration of which security mechanisms can be used across the API.
The list of values includes alternative security requirement objects that can be used. Only one of the security
requirement objects need to be satisfied to authorize a request. Individual operations can override this
definition. To make security optional, an empty security requirement ({}) can be included in the array.
A list of tags used by the specification with additional metadata.
The order of the tags can be used to reflect on their order by the parsing tools. Not all tags that are used by
the Operation Object must be declared. The tags that are not declared MAY be organized randomly or based on the
tools' logic. Each tag name in the list MUST be unique.
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.