David Osolkowski

@ashishdhingra I think I would need approval from our legal team to be able to share code publicly, but basically any ASP.NET Core application will do, including the example from...

@ashishdhingra it looks like it was fixed by @normj in PR #1017, so I believe this issue can be closed now.

I understand the restriction for auto-generated keys, but we're not trying to make use of that. We cannot provide a hash when first calling `withLDProvider`, because that has to occur...

The JavaScript SDK `LDClient` could decouple initialization from instantiation so that it waits until it is provided with user information and a hash to try contacting the server and avoid...

Our solution, which worked out fine, is to just use the plain JavaScript SDK and integrate with it manually. We already had a React context containing authentication state for our...

We've been hitting this for a while, in our case it's error E3002 Invalid Property when using `Fn::Transform` to import container definitions for an ECS task definition.

That's certainly a problem, but in my case I'm using English and it still didn't work, so there's something else going wrong as well.

I experienced this same issue as well. It's especially confusing because the fonts are visible in Word and work fine there, but putting the same font name in Terminal appears...

Not all of these are necessarily from underlying tools. For example: ``` npm WARN deprecated [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates. ``` appears to...

This is especially confusing because `dotnet build --help` still lists this as an available option. ``` -r, --runtime The target runtime to build for. ``` Options should not be listed...