-
-
Notifications
You must be signed in to change notification settings - Fork 528
Relative referenced yaml files results in a never type #1397
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
Comments
v6 supports remote schemas; this may just be a small bug in this specific scenario. Will investigate. Also give v7 ( |
Strange—I copied & pasted your exact schemas and I was not able to reproduce your error (on Node 18.12 as well as Node 20). I was seeing the file generate correctly. Maybe there’s something else going on that’s not captured in your reproduction (which was very helpful by the way, but I think there’s another issue here)? |
It's similar for my problem. I have remote root yaml, but referenced yaml doesn't show their types. Bumped to 6.7.0
In v7 next.2 it gives me types.Buy have strange things like |
@omgpiu sometimes the 7.x generates more |
This issue is stale because it has been open for 90 days with no activity. If there is no activity in the next 7 days, the issue will be closed. |
This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem. |
Description
Relative referenced yaml files results in a never type.
openapi-typescript
latest
(npx)18.12.1
macOS 13.4.1
Reproduction
foo.yaml
bar.yaml
cli command
Expected result
schema.d.ts
where
external["bar.yaml"]["components"]["schemas"]["User"]
is a normal type.Actual result
schema.d.ts
Checklist
npx @redocly/cli@latest lint
)So, is it possible to handle types in
bar.yml
?The text was updated successfully, but these errors were encountered: