Results 593 comments of Stephen Haberman

I almost filed this issue again b/c I'm looking at ts-mockito again and this is still a blocker. I.e. in test code like: ```typescript it("uses a mock", () => {...

We're prototyping a new project on tsdx and after an ~hour of fighting "why does `jsxImportSource`" not work (for emotion setup), it turns out tsdx was using its own shadowed...

@MattBodey AFAICT that doesn't work, b/c `npx` knows to download `mrm` (which is great) but neither `npx` nor `mrm` know to download `@my-org/my-task`, so you need to explicitly `npm i...

@kevinkhill personally publishing tasks to npm wasn't a big deal for us. Really great to hear you're poking around at mrm internals though! Its a great project.

@kevinkhill ah yeah, I get that. When I used to do Java projects back in the day, publishing to Maven central (their npm) was a huge PITA (mostly b/c Maven...

@nomadoda we're using (prototyping) `graphqlgen` with a patched `graphql-import` that I believe would support your structure with `schema: ./src/modules/`: https://github.com/prisma/graphql-import/pull/246 The trailing `/` on `./src/modules/` tells the patched `graphql-import` to...

I tried going all the way back to 2.20.0 just for kicks and it's broken with the same error: ``` "graphql-download": "npx [email protected] schema:download --endpoint=https://..../graphql schema.json", ``` I thought using...

Naive suggestion, but just prefixes? ``` export const UserResolverDefaults = { id: (parent: User) => parent.id, }; export type UserIdFieldResolver = ( parent: User, args: {}, ctx: Context, info: GraphQLResolveInfo...

Peanut gallery: I really like the file-per-resolver output. Bonus points if I had `schema/dir1/Foo.graphql` `schema/dir2/Bar.graphql` and they ended up as `generated/dir1/Foo.ts` `generated/dir2/Bar.ts`, e.g. the folder structure of our input graphql...

FWIW bikeshedding names a bit, but even with the per-file outputs, I wouldn't mind/would generally prefer prefix-based type names. E.g. for a given `Foo` graphql type, in its `graphqlgen`-generated `foo.ts`...