PascalSenn

It does preserve the order. The problem was that I didn't handle OrderBy and ThenBy properly. For my case it does work. Json serializers should preserve the order. At least...

@Yogu > "GraphQL Objects represent a list of named fields, each of which yield a value of a specific type. Object values should be serialized as ordered maps, where the...

Have a look at #62 This would solve the issues: ```graphql query{ servers( orderBy: { active: DESC assetNumber: ASC customer: { name:ASC } } ) { id active assetNumber customer...

great work @tomphilbin ! I wish every feature request would look like this! This got me thinking today. Together with execution plan this could become even more powerful. If we...

@MattMinke you know that you can configure the http client factory? you can also configure the http client builder as the third argument of `ConfigureHttpClient` https://chillicream.com/docs/strawberryshake/networking/authentication#http

@jkears at the moment this is not possible. How would the mongo query look like if you would issue one? Also, do you mind filtering in memory? this would be...

@jkears okok. so opting for the aggregation pipeline.. i mean, could work. Has other issues of course ;) like scalability of queries. But depending on the document you receive this...

mybad `[UseFiltering(Scope = "queryable")]`

@invzz thanks for reporting. We are working on a better ef core integration. At the moment we do not know if EF Core (and what Features of EF Core) is...

ah you use Automapper? because then this is probably the issue