Chris Lambe

I actually just ran into this issue as well, providing `null` as a managed value. Minimal reproduction: ```typescript import 'reflect-metadata'; import { container } from 'tsyringe'; container.register('foo', { useValue: null...

@avin-kavish I ended up just doing this: ```ts container.register('foo', { useFactory: instanceCachingFactory(() => possiblyNullishValue) }); ``` And it seems to work fine, though I suspect there's probably a reason _not_...

In the meantime, I've been accomplishing this with the following (admittedly verbose) typing: ```typescript queryBus.execute< FooQuery, Awaited >(new FooQuery(fooId)) ``` `Awaited` type comes from TypeScript 4.5.

This appears to be a documentation issue. Per the advice in https://github.com/renke/import-sort/issues/101, I was able to fix this by installing `import-sort-parser-typescript` and adding a config to `package.json`: ```json "importSort": {...

I'm interested in this as well! Years of using VS Code has wired my brain to cmd+shift+p for the command palette.

Not that I necessarily disagree with your styling changes, but it seems like a pretty sure way to get this PR rejected/ignored. I would love to see this change incorporated...

I would love to have this for picking a database environment (e.g. `local`, `dev`, `staging`, etc.) when using `pgcli`. Maybe if the plugin has been `init`'d with multiple credentials it...

I did some `git bisect`ing and tracked the problem down to this commit: https://github.com/Effect-TS/effect/commit/bc7efa3b031bb25e1ed3c8f2d3fb5e8da166cadc#diff-956ed42947ebb72a495a619a3989f3ee9b1d17f5f7575fe3e12690278e6e8483

As a workaround, using `any` as the input type instead of `unknown` will circumvent the typing error: ```ts import { Match } from "effect" const match = Match.type().pipe( Match.withReturnType(), Match.when({...