Repository navigation
$ref is not a valid property path item #288
Description
Hi,
I tried 1.1.0-preview.3 reader version with this sample:
components:
securitySchemes:
Token:
description: This API uses OAuth 2
flows:
implicit:
authorizationUrl: https://.......
scopes: []
tokenUrl: https://.......
type: oauth2
info:
title: API
version: 0.9.0
openapi: 3.0.0
paths:
/float:
$ref: paths/float.yaml#/collection
/float/{id}:
$ref: paths/float.yaml#/individual
/float/{id}/tags:
$ref: paths/tags.yaml#/network_collection
security:
- Token: []
servers:
- url: /v1And I get errors like $ref is not a valid property at #/paths//float
I checked the specification and it should be permitted.
Thanks
Activity
darrelmiller commentedon Jun 21, 2018
Yes it should. However, in v1.0 we don't support referencing external files, so we weren't able to support $ref in PathItem. But you we shouldn't flag it as an error. I will get that fixed in the 1.1 version so it doesn't fail. It will probably be the 1.2 version before we get the multi-file support.
talamram commentedon Jun 24, 2018
Hi,
First, Thanks :)
Second, do you have any timeline for supporting referencing external files?
Thanks
darrelmiller commentedon Jun 25, 2018
talamram I wish I did. I would love to get it out within the next few weeks, but it just depends on how much free time I get. And I want to get the Swashbuckle support for V3 finished first.
fabianmeyer commentedon Feb 10, 2020
Hi, any update on this issue?
darrelmiller commentedon Feb 10, 2020
Fabian Meyer (@fabianmeyer) Sadly I have no good news. The inlining of references took priority over finishing OpenAPIWorkspace and getting support for external references. Hopefully, that can be next up.