When working with a deeply nested multi-file OpenAPI spec, $ref paths become very long and hard to maintain:
$ref: '../../../../../components/schemas/requests/orders/order_items.yaml#/OrderItems'
This breaks easily on any directory restructure and hurts readability.
Would it be possible to support any of the following?
-
Root-relative paths — $ref resolved relative to the root openapi.yaml, e.g.:
$ref: '/components/schemas/requests/orders/order_items.yaml#/OrderItems'
-
Path aliases — configured in zudoku.config.tsx, e.g.:
aliases: { '@schemas': './apis/components/schemas' }
so refs like $ref: '@schemas/requests/orders/order_items.yaml#/OrderItems' work.
When working with a deeply nested multi-file OpenAPI spec,
$refpaths become very long and hard to maintain:This breaks easily on any directory restructure and hurts readability.
Would it be possible to support any of the following?
Root-relative paths —
$refresolved relative to the root openapi.yaml, e.g.:Path aliases — configured in zudoku.config.tsx, e.g.:
so refs like
$ref: '@schemas/requests/orders/order_items.yaml#/OrderItems'work.