Currently, RC1 defines a merging algorithm that helps people to understand how the merging of traits (and similar for resource types) works. In RC2 we should simplify that a bit more and add an example like the following:
resourceTypes:
collection:
get:
description: just a test
headers:
APIKey:
/resource:
type: collection
get:
description: override the description
responses:
200:
body:
application/json:
The only overlay between the collection resource type and the resource declaration is description which is defined in both. In this example, the final version will have the description that has been explicitly defined in the resource.
Every explicit node will win over the ones that are declared in a resource type or trait. The rest get's simple merged. The final merged result must be:
VasiliyLysokobylko
commented
8 years ago
Currently, RC1 defines a merging algorithm that helps people to understand how the merging of traits (and similar for resource types) works. In RC2 we should simplify that a bit more and add an example like the following:
The only overlay between the
collectionresource type and the resource declaration isdescriptionwhich is defined in both. In this example, the final version will have the description that has been explicitly defined in the resource.Every explicit node will win over the ones that are declared in a resource type or trait. The rest get's simple merged. The final merged result must be: