-
Notifications
You must be signed in to change notification settings - Fork 3
ResolvableSelector supports parse addr and extractor options #8
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
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
service_name_extractor.go
Outdated
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.
Confirm whether the changes in this file have been refactored?The code before the change seems to be more readable than the code after the change.
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.
fixed
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.
LGTM
* update badges (#4) * update badges * fix typo * Update README.md (#5) * Update README.zh_CN.md (#6) * add issue template (#7) * ResolvableSelector supports parse addr and extractor options (#8) * all: ResolvableSelector supports parse addr and extractor options * all: revert service_name_extractor change --------- Co-authored-by: MengYinlei <43751910+YoungFr@users.noreply.github.com>
In order to allow for more precise control over the
ResolvableSelector
fromthe outside, we have added the
ParseAddr
andExtractor
options to it.