Michael Staib

icon indicating a website link http://www.chillicream.com icon indicating an email [email protected]

icon company ChilliCream icon location Zurich icon location GraphQL Technical Steering Committee | Microsoft MVP | Author of Hot Chocolate | https://twitter.com/michael_staib

Results 571 comments of Michael Staib

Introduce `MaybeSet<T>`: A better version of `Optional<T>`

We are discussing a new `PatchInputType` at the moment. The idea described here has to many issues we see, but we recognize the need for a higher level patch type....

ResolveWith<> Fails when an interface is specified in 13.1+ As a Non Abstract Class is Required

I have to look at this again. In my mind I never expected people to hook interfaces in here.

Adds the limit for the deferred stream's queue size

We still have this on the back log. I will soon start work on the defer / stream part and then we will have a look at this.

Transaction committed on domain error for request with multiple mutations

I had a stab at this one and we have a rough idea but it also has a lot of implications. To stop the mutation flow here we actually need...

Transaction committed on domain error for request with multiple mutations

I am moving it to 13.9

Add header to disable null-bubbling

This would create a non-spec compliant GraphQL server. We have discussed this in the working group and all agreed that it should not be a default in a GraphQL server....

Add header to disable null-bubbling

You can adopt the new spec directive, but having it as default is not a good idea.

Add header to disable null-bubbling

However, with a header you can move this into the network layer and no one has to think about it.

Add header to disable null-bubbling

Can you post a link to the rfc?

Add header to disable null-bubbling

Lets see ... what I can include is a header approach at the moment. I can see that we include the draft with V14 but the new syntax `!String` seems...