Routing context support in uri #168
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
zhenlineo
force-pushed
the
1.3-routing-context
branch
2 times, most recently
from
ef212fb
to
cbb42c0
Compare
lutovich
approved these changes
Apr 20, 2017
| { | ||
| public class NetworkExtensionsTests | ||
| { | ||
| public class ParseRoutingContextMethod |
There was a problem hiding this comment.
Maybe also include tests without port, without routing params and for uri like this bolt://localhost/? because it is also a valid one.
zhenlineo
force-pushed
the
1.3-routing-context
branch
4 times, most recently
from
0ae6d93
to
af6d417
Compare
added 5 commits
April 21, 2017 14:08
Made driver aware getRoutingTable in 3.2+ server Made driver parse routing context from uri TODO: tests in ClusterDiscoveryManager
zhenlineo
force-pushed
the
1.3-routing-context
branch
from
af6d417
to
a206309
Compare
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.
Made driver aware getRoutingTable in 3.2+ server
Made driver parse routing context from uri