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
When trying to generate types on Windows and using a full filepath as the output it will error. It does not have the same issue for the input path. If you change the output path to something like ./output.d.ts or ../output.d.ts it seems to handle those fine.
The issue seems to be here where you are trying to create a new URL based on the output file but trying to prefix it with . which will error when given a full path instead of a relative path.
Description
When trying to generate types on Windows and using a full filepath as the output it will error. It does not have the same issue for the input path. If you change the output path to something like
./output.d.ts
or../output.d.ts
it seems to handle those fine.The issue seems to be here where you are trying to create a new URL based on the output file but trying to prefix it with
.
which will error when given a full path instead of a relative path.openapi-typescript/packages/openapi-typescript/bin/cli.js
Lines 205 to 207 in 45cea6b
openapi-typescript
7.0.2
20.15.0
Windows 11
Reproduction
Try to generate a types file with a full filepath on Windows such as
C:\Users\User\Desktop\output.d.ts
Expected result
It shouldn't error and should support the path like any other
Checklist
npx @redocly/cli@latest lint
)The text was updated successfully, but these errors were encountered: