Sergei Iarkin
Sergei Iarkin
## Problem There is a [convention](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties) about using `status.conditions` for higher-level status reporting from a controller. As it should a list of objects, it becomes harder to update one element...
As per code [of `Absinthe.Resolution.call/2`](https://github.com/absinthe-graphql/absinthe/blob/master/lib/absinthe/resolution.ex#L204-L212) three different forms of resolution function are supported, type spec `resolver_t` is updated accordingly to this.