-
Notifications
You must be signed in to change notification settings - Fork 0
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
Updates for DDN Alpha and TypeScript Deno connector compatibility #1
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. The subgraph stuff certainly adds a lot of files, but given that this is primarily an example repo I think that's fine. If only there was some way to make sure it stayed in sync with any future format changes...
{ | ||
"deno.enable": true, | ||
"deno.lint": true, | ||
"deno.unstable": false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're using unstable features in the connector to support the NPM modules so should we try to match this with the dev tools?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure that refers to that, I think this enables access to Deno's unstable APIs. I've used an NPM package (for testing) in this project with that set to false and it works just fine.
COPY ./functions /functions/src | ||
|
||
# Pre-cache inference results and dependencies | ||
RUN PRECACHE_ONLY=true /app/entrypoint.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
75d3ba7
to
cc37e1d
Compare
This PR updates this repo to be compatible with the DDN Alpha and also with the latest TypeScript Deno connector compatibility (namely the improved watch support, introduced in hasura/ndc-typescript-deno#79).
errors
property is not nullable/undefined on the return object, because the TypeScript Deno connector doesn't support nullable/undefined types properly yetconfig.json
file deleted and an empty config just inlined into the CLI commands in the readmeextensions.json
has been added to recommend the required VSCode extensionssettings.json
added to ensure Deno extension is activated in this repo