Middleware can not add errors to execution context without raising an error

[Dan]

Use case: I've written a middleware for limiting users to a daily quota of nodes. The middleware counts nodes of particular types we care about limiting, and when the user hits their limit the middleware will raise an exception saying that they've hit their limit.

This works great, except in the case of lists. In this case, we are returning to the user as many elements of the list as possible until they go over the limit, and then no more. In this case, the middleware can not raise an exception because that would prevent it from also returning the promise for the truncated list of data.

Ideally in the middleware I could call execution_context.report_error() from https://github.com/graphql-python/graphql-core/blob/b3a6bd0f89651af10a937e5270e46c696672a2e5/graphql/execution/base.py#L92 to add an error saying "your limit was hit, and list field XYZ has had its data truncated" to the list of reported errors, but then continue along and return the truncated list of data.

[Dan]

It looks like #153 would also solve this.

[Nick Harris]

I think my PR for exposing extensions might also solve this problem. https://github.com/graphql-python/graphql-core/pull/205. This optionally allows middleware to return the ExecutionResult object which in theory would allow you to set both an error and data object as the return value.