Traps & Friction Points

[jasonkuhrt]

We have consolidated the issues in this epic to an organized notion table. It is public.

• Update examples docs/examples to hook nexus generate on post install hook #6
• Allow anonymous event logs graphql-framework-experiment#284
• chore(deps): update dependency @types/jest to v24.9.0 graphql-framework-experiment#285
• chore(deps): update dependency husky to v4.0.10 graphql-framework-experiment#286
• Add persisted logs graphql-framework-experiment#288
• fix(cli): exit with code returned by command graphql-framework-experiment#281
• doctor command check for --types compiler option graphql-framework-experiment#2
• build command mvp graphql-framework-experiment#3
• dev command graphql-framework-experiment#4
• init command graphql-framework-experiment#5
• Use TS language service plugin to improve autocomplete graphql-nexus/nexus-plugin-prisma#506
• Refine plugin API for watcher graphql-framework-experiment#289
• chore(deps): update dependency husky to v4.0.8 graphql-framework-experiment#277
• Use proxies to avoid not defined error blocking compile graphql-nexus/nexus-plugin-prisma#472
• Facade package @prisma/photon prisma/prisma-client-js#261
• chore(deps): update dependency husky to v4.0.4 graphql-framework-experiment#253
• [cli] seed command graphql-framework-experiment#275
• Integrate typegen into plugin system graphql-nexus/nexus-plugin-prisma#507
• Synchronous testing functions graphql-framework-experiment#292
• Print nicer error messages (with callsites) graphql-nexus/nexus-plugin-prisma#479

When this issue is resolved we should be able to mark the following as resolved too:

• feat: scaffold tsconfig is none is present graphql-framework-experiment#77
• feat: support for now deployments graphql-framework-experiment#146

[jasonkuhrt]

@Weakky

🔵 Forgetting to run Server (thus generating new typings)
prisma-labs/graphql-framework-experiment#77 (comment)
💡Have a separate process always generating typegen

What does that solution mean/how could it help exactly?

🔵 No type-checking after cloning a repo
💡 Use postInstall npm hook to run nexus typegen

The best we could do with that solution is for it to be a pattern we suggest right? Since it would be app-level.

Cons: Less composable. We already have composability issues with t.field

We could allow the object version too, thus being backwards compatible. And that is nicer for machine use-cases as we identified the other night with t.field.

🔴 Runtime error prevents typegen from being re-run, thus making the typechecking desync/broken

How could this be fixed, though?

[Weakky]

What does that solution mean/how could it help exactly?

We could, for instance, have a VSC plugin running the typegen in the background, so that it's independent of the runtime.

The best we could do with that solution is for it to be a pattern we suggest right? Since it would be app-level.

Yes. "Encoding" that pattern in all examples + documenting it might be the best solution here

We could allow the object version too, thus being backward compatible. And that is nicer for machine use-cases as we identified the other night with t.field.

Still wondering whether it's a good idea to have two APIs to achieve the same thing. Might be confusing for users

How could this be fixed, though?

I don't think we can, hence why I labeled it as 🔴 (Trap)

[jasonkuhrt]

More since here graphql-nexus/nexus-plugin-prisma#523

[ujwal-setlur]

Would love a VSC plugin to generate types