Jonathan Ehwald

What kind of patch could that be? Looks like those `.chk` files are always called the same as the `.so` files they belong to. `linuxdeployqt` determines what `.so` files the...

> If it is defined as `Any`, please emit `String` as GraphQL schema and serialize it with `str()`? > > For my case, I am not making a class for...

Hey @staubina, with our current implementation this seems to be expected. ~You might want to try to add your validation error to the execution context, similar to how our built-in...

> I missed your reply before answering! I think this won't work well because we'd have parsed the query by then, and we want to prevent to parse huge strings...

> So you'd suggest to only handle GraphQL errors in our execute function? Wondering about that too :) At least from the perspective of integrations, all "normal resolvers errors" are...

> I think so too, we already treat any error inside resolvers as GraphQL errors, it is weird to not do that for parsing and operation errors 😊 > >...

> I was able to get the following to work for now. Good job! You're correct, supplying a result from within the `on_excute` hook will prevent further evaluation. This is...

Thanks for reporting @ancs21! We can adjust the code to handle missing subprotocols more gracefully. However, I'm not sure whether we want to reject the websocket connection in this case...

Make sure your react-native-paper `` is nested inside the react-navigation ``, not the other way around.

Hi @wlaub, thanks for reporting! This one is tricky. You're using the deprecated legacy `graphql-ws` websocket subprotocol for subscriptions which has a pretty bad [protocol specification](https://github.com/apollographql/subscriptions-transport-ws/blob/master/PROTOCOL.md). This specification does not...