Change Go interceptors order #85
Merged
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.
Part of #84.
While migrating lookout I noticed that we can't use
pb.AddFieldsinside a client interceptor. This is becausepb.DialContextWithInterceptorswas executingCtxlog*ClientInterceptorbefore the user provided ones.With the change in this PR the interceptors are called in this order:
Instead of the previous one:
@se7entyse7en can you please check if we can have a similar problem in the python API?