io.atomicbits.scraml.ramlparser.lookup
The canonical lookup map.
The types that are explicitely declared the in the Raml model's types declaration and those that are implicitely declared inside the resource's parameters (e.g. GET parameters) and body content of responses and replies. Each type declaration is keyed on its native (RAML) id.
Like parsedTypeIndex, but the elements in this index will not be used directly to create canonical types later on. This index will only contain the Selection elements of a json-schema object. We need to be able to look up those elements, but we will generate their canonical form through their parent.
Native references may be used in the RAML definition to refer to json-schema types that have their own json-schema id internally. This map enables us to translate the canonical name that matches the native id to the canonical name that matches the json-schema id.
Native references may be used in the RAML definition to refer to json-schema types that have their own json-schema id internally.
Native references may be used in the RAML definition to refer to json-schema types that have their own json-schema id internally. This map enables us to translate the canonical name that matches the native id to the canonical name that matches the json-schema id.
The canonical lookup map.
The types that are explicitely declared the in the Raml model's types declaration and those that are implicitely declared inside the resource's parameters (e.
The types that are explicitely declared the in the Raml model's types declaration and those that are implicitely declared inside the resource's parameters (e.g. GET parameters) and body content of responses and replies. Each type declaration is keyed on its native (RAML) id.
Like parsedTypeIndex, but the elements in this index will not be used directly to create canonical types later on.
Like parsedTypeIndex, but the elements in this index will not be used directly to create canonical types later on. This index will only contain the Selection elements of a json-schema object. We need to be able to look up those elements, but we will generate their canonical form through their parent.
The canonical lookup map.
The types that are explicitely declared the in the Raml model's types declaration and those that are implicitely declared inside the resource's parameters (e.g. GET parameters) and body content of responses and replies. Each type declaration is keyed on its native (RAML) id.
Like parsedTypeIndex, but the elements in this index will not be used directly to create canonical types later on. This index will only contain the Selection elements of a json-schema object. We need to be able to look up those elements, but we will generate their canonical form through their parent.
Native references may be used in the RAML definition to refer to json-schema types that have their own json-schema id internally. This map enables us to translate the canonical name that matches the native id to the canonical name that matches the json-schema id.