fix(graphql): Change config from raw path to file: url
#9311
Conversation
This change is based on what is done for payload types generation: https://github.com/payloadcms/payload/blob/main/packages/payload/src/bin/index.ts#L54
|
Not sure how to write a regression test for this, as it's platform specific. Could involve modifying |
|
This commit doesn't touch anything involved in the e2e file upload tests, so I suspect something was failing in the beta I forked off of. I updated my branch to current main, which hopefully will fix the failing tests. |
|
I hope this gets sorted out soon. Since I upgraded to payload v3 I can't generate schemas. |
|
@Arcane36 Hopefully soon! It's a pretty simple fix. We ended up just using patch-package in the meantime. Basically, see what my commit changes, and then make that same change in your node_modules to the built js for the payload-graphql package. Then you can generate the patch and keep it in your version control so your team gets the patched version too. |
|
Thanks for the fix @6TELOIV, works like a charm! I hope this will be merged soon. |
What?
On windows, the
payload-graphql generate:schemacommand fails.Why?
Because the config it's trying to load is
c:\path\to\config.js, which node interprets as\path\to\config.json thec:protocol.How?
By changing it to use a file URL, as in
file:\\\c:\path\to\config.js. The change is the same as what the mainpayloadcli does: https://github.com/payloadcms/payload/blob/main/packages/payload/src/bin/index.ts#L54Fixes #9309