Andrii Chebukin

Before | Method | Mean | Error | StdDev | Median | Min | Max | Op/s | Gen0 | Gen1 | Allocated | |------------------------------ |-------------:|-----------:|-----------:|-------------:|-------------:|-------------:|----------:|--------:|-------:|----------:| | BenchmarkSimpleQueryUnparsed | 85.76...

Added `FieldDef<'Val, 'Res>` to support resolver changing middlewares

2

In order to call `Define.Field

`ID` type deserialization fix with field tests

1

@ivelten I think testing should happen from here. Also, we can change some `id` fields on StarWars API to cover different scenarios

Fixed `ID` type deserialization

6

Rebase of #262

https://github.com/graphql/graphql-over-http https://graphql.github.io/graphql-over-http/

### Description Requested fields influence the cache timeout for a request. We can add `@cacheControl` as described [here](https://blog.logrocket.com/http-caching-graphql/) to address that ### Expected behavior Minimum `maxAge` is used among all...

https://github.com/meziantou/Meziantou.Xunit.ParallelTestFramework

Both `AbstractionTests.fs` and `UnionInterfaceTests.fs` do the same work but a bit differently. They should be merged into one file

@id or @unique directive

1

Dgraph has a [directive ](https://dgraph.io/docs/graphql/schema/ids/) that ensures a unique field value. Do we need a directive like that?