Chris Sauve
Chris Sauve
- [ ] codesandbox - [ ] glitch (https://twitter.com/_developit/status/1389287149934100483) - [ ] runkit
https://docs.netlify.com/functions/configure-and-deploy/ https://docs.netlify.com/functions/build-with-javascript/#unbundled-javascript-function-deploys https://docs.netlify.com/configure-builds/file-based-configuration/#build-settings https://docs.netlify.com/routing/redirects/rewrites-proxies/ https://docs.netlify.com/site-deploys/create-deploys/
Right now, there is no indication of what project/ schema a given type definition is for when we print it to the CLI. We should show some of that context!
Thought of while reading https://marcus.io/blog/improved-accessible-routing-vuejs
The web team found that `buildClientSchema` could shave off almost a second per test file, compared to parsing the schema SDL. Might warrant some sewing-kit helpers to make sure that...
