Roman Sharkov

CI's complaining.. I'll try to look into it ASAP

The [api/gqlshield](https://github.com/romshark/dgraph_graphql_go/tree/master/api/gqlshield) package can actually be used as a stand-alone library: https://play.golang.org/p/yf0Zs8AJk_2 I haven't had the time to write a complete documentation for it yet but its [interface](https://github.com/romshark/dgraph_graphql_go/blob/baaa70b97f4d9ba9d851cfb45bff85ff2a7ff35a/api/gqlshield/gqlshield.go#L25) is pretty...

Another problem of this particular approach to whitelisting is the lack of flexibility. A whitelist should protect the API from overly complex queries, but what if the whitelist looks like...

@winterale query cost analysis is really cool but it's somewhat more complex. You can, of course, just assign a static cost to each and every field and then fine-tune it...

I'm planning to implement this functionality in later releases. BTW, Posts and reactions won't actually be _deleted_, just _removed_ (archived). But I'm not yet sure how it should work. Let's...

Actually, It's not so easy. Imagine spending hours writing a reaction just to suddenly realize it's lost due to the author of the superordinate post/reaction removing it. It can be...

@winterale - you already can create reactions on reactions. - yep, if the post/reaction a reaction was created for is removed then it should just be hidden

This is not a priority task since Go modules are still experimental until Go 1.13

This API feature is being worked on in the [pagination branch](https://github.com/romshark/dgraph_graphql_go/tree/pagination) right now.

This feature is stalled due to [dgraph/#3472](https://github.com/dgraph-io/dgraph/issues/3472) and [dgraph/#3473](https://github.com/dgraph-io/dgraph/issues/3473). Pagination should be done using indexed cursors which seems to be broken right now. `offset`-based pagination, which is the current implementation,...