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.
New issue
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
Provide a way to customize context propagation using its own storage #2610
Provide a way to customize context propagation using its own storage #2610
Changes from 3 commits
5488ed0
b9c59b6
3472811
cf3dd19
10dab88
530e2d5
9fd12e5
1f57707
cdec669
6e415d9
9b9b64a
63ffc15
ccf427a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I was thinking instead of loading directly from the flag, we'd use the flag to disambiguate among the different providers in this case. I guess we can do both though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I guess I totally misunderstood. 🤣
So you meant when multiple providers exist (e.g
com.x.AProvider
,io.x.BProvider
...), if the flag isio.x.BProvider
, then we should choose theBProvider
class. Right?If so, I want to get rid of the current way and follow it because, I think, there would be a case who wants to use two different JARs that have their own
RequestContextStorage
.So I think we should choose one of them instead of throwing an exception. 😉