add registry protocol config #90
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## develop #90 +/- ##
========================================
Coverage 42.01% 42.01%
========================================
Files 33 33
Lines 1409 1409
========================================
Hits 592 592
Misses 733 733
Partials 84 84
Continue to review full report at Codecov.
|
cityiron
approved these changes
Dec 23, 2020
zhangshen023
approved these changes
Dec 27, 2020
yqxu
approved these changes
Dec 28, 2020
tydhot
pushed a commit
to tydhot/dubbo-go-pixiu
that referenced
this pull request
Nov 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does:
when i have two zk registry , i can't use it , beacuse there is a map for registry config and registry type is key
this pr will fix it
Which issue(s) this PR fixes:
Fixes #89
Special notes for your reviewer:
Does this PR introduce a user-facing change?: