You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem description
Not using $ref towards a common schema needs to be motivated by the need for a specific local variant of a schema, and also requires a dedicated local name of this schema, to avoid mixing with the common schemas.
Possible evolution
For common schema PhoneNumber use the $ref notation :
We have an alias in line 335 $ref: '#/components/schemas/PhoneNumber' which is then resolved to $ref: "../common/CAMARA_common.yaml#/components/schemas/PhoneNumber"
An alias is convenient when migrating an existing spec with local schema definitions.
The difference is one of style, not correctness.
For me we can think of simplifying API definition within the next release.
5. We have an alias in line 335 $ref: '#/components/schemas/PhoneNumber' which is then resolved to $ref: "../common/CAMARA_common.yaml#/components/schemas/PhoneNumber"
An alias is convenient when migrating an existing spec with local schema definitions.
The difference is one of style, not correctness.
For me we can think of simplifying API definition within the next release.
Activity
bigludo7 commentedon Oct 23, 2026
@tanjadegroot I'm bit lost - this is not already the case lines 339-340?
rartych commentedon Oct 23, 2026
We have an alias in line 335
$ref: '#/components/schemas/PhoneNumber'which is then resolved to$ref: "../common/CAMARA_common.yaml#/components/schemas/PhoneNumber"An alias is convenient when migrating an existing spec with local schema definitions.
The difference is one of style, not correctness.
For me we can think of simplifying API definition within the next release.
bigludo7 commentedon Oct 23, 2026
OK ! I've done #251
Is is what you expect? :)