"Could not fetch schema" error when using a reference Schema in Windows (works well in POSIX systems)

[javierjim]

Hey there. I'm opening this issue since I am seeing the same problems as #921

However, I think this has to do with how paths work in POSIX systems. In my case, this works perfectly in MacOS, Ubuntu, and WSL (Windows Subsystem for Linux). It does not work on Windows when using command prompt.

A fix would be great, but more than that I am looking to see if -in fact- Windows is not a supported platform.

Even if I try to replace forward with backward slashes quicktype fails with the same issue.

Any pointers are appreciated.

[schani]

I retested this on current master (commit 662ad5b). This was a genuine Windows-only bug: the URI parser we used treated a Windows drive letter (like C:) as a URI scheme, which mangled relative $ref targets into bogus HTTP addresses and produced the "Could not fetch schema" error. It was fixed by PR #2886 (issue #2869), which added Windows path handling (fixWindowsPath/filePathFromFileURI) used by the schema input and file I/O code, with unit and end-to-end regression tests.

Running something like node dist/index.js -s schema 'C:/Users/quicktype/top.schema.json' -l typescript against a schema with a relative $ref now resolves the referenced schema correctly, and both C:/... and C:\\... path forms work. This fix will be in the next release. If you can still reproduce the problem on a current build, please reopen or comment with details and I'll take another look.