Mithras
Mithras
Alright, sorry for spamming. This PR is pretty much what we use today in an internal company package and I just really want to merge this into graphql-dotnet so that...
@sungam3r I'll refactor federation to use new printer. It shouldn't be too complex as long as the new one allows overriding the same methods or, even better, separate methods that...
Rebased on latest master
related https://github.com/graphql-dotnet/graphql-dotnet/pull/3144
I'm experiencing the same problem with `apollo-gateway`. For now I've just monkey patched `graphql` like this:  I haven't tested it much but it seems to be working. I don't...
I'm also missing this feature. Right now I have to go to settings and check/uncheck some random checkbox to reset window sizes to default. So it's already possible, there is...
Appdaemon 3 was throwing exception. Appdaemon 4 is swallowing it - https://github.com/home-assistant/appdaemon/blob/dev/appdaemon/services.py#L113. Swallowing exceptions is the worst anti pattern ever.
Ignore the example. Ok, it might be a wrong line but in log I'm seeing > 2020-03-10 09:11:46.964798 WARNING HASS: Error calling Home Assistant service default/camera/record > 2020-03-10 09:11:46.965925 WARNING...
Anyway, there are 4 "return None" there. How do I even tell what's wrong? Why doesn't it just throw exceptions with adequate messages? Logging doesn't replace exceptions. Bad design.