Jim Isaacs

+1 researching issues I'm facing with corporate certs lead me here. Any news?

It's been a while since anyone has posted here, and I was wondering what the sentiment is today versus 3 years ago? Personally I think this was and still is...

You know, I ended doing this... ## my-project/utils/Application.ts ```ts import { FreshOptions, Manifest, ServerContext, StartOptions } from '$fresh/server.ts'; import { serve } from 'https://deno.land/[email protected]/http/server.ts'; const connInfo = { localAddr: {...

With the above in place, I can now test like this: ```ts /// /// /// /// /// import { assert, assertEquals } from 'https://deno.land/[email protected]/testing/asserts.ts'; import init from '../utils/init.ts'; const shouldMock...

I have just realized, this isn't a problem with `bootstrap`, but with `outdated`. I'm going to update this issue rather than closing and reopening a new one.

@Dimillian the code you shared is a bit uncanny to code that we've put together across ReSwift + ReKotlin. There's some differences, but I think we try to should share...

@Dimillian I should also mention an advantage of removing the store from components is that they become completely autonomous units of code, that can be tested as such.

Thanks for your help on this @hwillson !!!

What is this? ``` extension: ".graphql.interface.ts" # Matches the existing Apollo-Codegen file-naming ``` We've been using apollo for years now, and I've never seen this naming convention used in output.

Does the graphql codegen type names match apollo's? e.g. ``` OperationOrFragmentName_fieldName_fieldName_fieldName ``` Located in file: `flatPathOrFolderPath/OperationOrFragmentName.ts` I ask, because a significant deviation from this would hurt quite a bit.