Roman Ivantsov

ah, and about input types and mutations - in my app. There are around 40 types to be loaded/updated, so we recognized a problem from the start - we didn't...

Hi finally looked at this, and sorry it took so long. I have an answer, and I am afraid you not gonna like it. This update query is not supposed...

done, new version is pushed

Hi, and sorry it took so long. I am preparing update, and looked at this issue. It looks like it works correctly. I'm afraid there's some confusion here. The goal...

yes, it will be fixed as well, will try to focus on this and other general restructuring issues in the next few weeks. I will post more about the plans...

I will definitely look at that, no promises or dates yet, but I am looking at soft deletes

sorry for the delay but the problem #225 with expressions in GroupBy is fixed now

one simple solution - introduce static singleton (static string field); your FetchApiKey is no different from static field, and make FetchApiKey return it from static field. If field is empty,...

implemented, v 2.0 - Subscriptions are here!

that's an interesting trick they suggest, not sure it aligns with graphql standard and principles, never saw it used - to add a query field to Mutation object. It might...