Ivan Maximov

See: - [ ] https://github.com/graphql-dotnet/graphql-dotnet/pull/2283#discussion_r579871341 -- regarding AutoRegisteringObjectGraphType - [x] https://github.com/graphql-dotnet/graphql-dotnet/pull/2293#issuecomment-782935091 -- regarding custom scalars

Throw error on TypeSystemDefinition or Extension

2


Allow to apply @deprecated only in "right" places

2

See https://github.com/graphql-dotnet/graphql-dotnet/pull/2507#discussion_r614839990

Caching syntactically valid GraphQL document when GraphQL request contains invalid inputs

3

See https://github.com/graphql-dotnet/graphql-dotnet/issues/1950#issuecomment-797333677

Possible redesign of the request execution stage for GraphQL.NET v5

8

In version 4 (which we planned to release on February 1), we made many optimizations over version 3. Memory consumption has dropped quite dramatically, which is good news. It is...

[WIP] Strong typed API for building fields

15

Rel: #3574 and #1176. This is my attempt to solve the problem of excessive `StreamResolver` property for `FieldType` class and API around it. TODO: - Add APIs to use `ResolveStream`...

[DEMO] More AOT annotations

11

I tried to follow AOT annotations guidelines and I have a bad feeling about this all. Problems: 1. It is very toxic for code - even worse then async/await "infection"...

Move StreamResolver to new class

1

`StreamResolver` is allowed to be set only for root fields of subscriptions, i.e. too narrow case. Let's consider possibility of moving it into dedicated class like `SubscriptionRootFieldType : FieldType`

For v8, I would also like to require that `Resolver` is null when `StreamResolver` is not null. This would certainly be a breaking change, but it should clarify behavior, as...

CompatibilityLevel for introspection

1

> If `RepeatableDirectives` and/or other new features are going to break introspection queries, it is likely that some users will want to maintain compatibility with older versions regardless of what...