-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Schema referenced in patternProperties is not embedded in bundled file #792
Comments
Thank you for reporting this @arvidfm! However, this is not a bug but rather an enhancement as we don't support BTW, in your exact case you can use additionalProperties:
$ref: object.yaml |
This is still an issue. Tried to use $ref under patternProperties but it is not working. Example:
|
@amiika yes, this is still to be implemented. Maybe you can try using |
Adds a script to rewrite part of the bundled API spec, to work around Redocly not having support for `patternProperties` (see also bug Redocly/redocly-cli#792)
Adds a script to rewrite part of the bundled API spec, to work around Redocly not having support for `patternProperties` (see also bug Redocly/redocly-cli#792)
@tatomyr do you know if this is something that will be supported soon? |
The fix is coming through. Thanks, @kevin-lithic, for bringing it to my attention! |
Describe the bug
References to schemas defined in external files do not get embedded in
components
if present in apatternProperties
definition of an object. Instead, the$ref
still points to the external file even after bundling.To Reproduce
Steps to reproduce the behavior:
.redocly.yaml
fileopenapi/openapi.yaml
openapi/object.yaml
openapi bundle -o dist
The resulting
dist.yaml
contains:Note how the reference to
object.yaml
is still there.Expected behavior
The referenced schema should be embedded, something like:
Logs
If applicable, add logs to help explain your problem.
OpenAPI definition
See above
Redocly Version(s)
What version of Redocly CLI are you using?
Node.js
Version(s)What version of
node.js
are you using?Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: