Add resolver middleware Add opentracing support #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a user specified resolver middleware stack and some opentracing resolver middleware that uses it.
The middlware stack probably goes a long way towards #39, allowing middlware to be defined around the user defined resolvers. It will not be called around any directly bound models fields or methods.
example usage:
weakly typed interface but there is an assertion in the generated code as soon at it returns. This is mostly to allow access to the error on the way through. Unmarshaled args are now in resolver context, and can be manipulated before calling next.
The dataloader example now hosts an appdash instance to see the metrics collected. Here is an example of running