We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For various reasons (e.g. experiments) it might be useful to wrap interceptors.
The problem is that once an interceptor gets wrapped, it will not be matched to its configurations anymore.
I propose to add the following feature:
When a Mux is constructed we match configs with their interceptor, but we also check if the the interceptor has a
Unwrap() Interceptor
method on it.
If so, we recursively check configs against the inner interceptors.
The text was updated successfully, but these errors were encountered:
Add support for wrapped interceptor, detect config clashes.
6240b2e
Fixes #302, #307
a7648cc
62623f4
Is my understanding correct that we don't need anything extra to support this case? Maybe just a GoDoc example?
Sorry, something went wrong.
empijei
No branches or pull requests
For various reasons (e.g. experiments) it might be useful to wrap interceptors.
The problem is that once an interceptor gets wrapped, it will not be matched to its configurations anymore.
I propose to add the following feature:
When a Mux is constructed we match configs with their interceptor, but we also check if the the interceptor has a
Unwrap() Interceptor
method on it.
If so, we recursively check configs against the inner interceptors.
The text was updated successfully, but these errors were encountered: