Closed erunion closed 1 year ago
For meta keywords like title, description, $id, $schema, default the strategy is to use the first possible value if there are conflicting ones. So the root schema is prioritized. This process possibly removes some meta information from your schema. So it's lossy. Override this by providing custom resolvers.
There is no good way to merge these values, So it picks the first one. You can override this by providing a custom resolver for the description keyword.
Should the order of the items in an
allOf
matter for adescription
property override? Seems that if adescription
is a lone schema in the second part of anallOf
that it's ignored.