Support for module-based read-only commands #2401 #2447
Closed
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.
Make sure that:
Mark,
Looking for feedback on this. At this point, I've authored the code changes, but no unit/integration tests have been written.
A few questions:
extraReadOnlyCommands
. I'd really rather do something that also pulls in the standard read-only commands and combines the functionality directly. I also wasn't sure that this is what you were expecting.ClientOptions
logic in theClusterClientOptions
to automatically pick up the cluster read-only commands - however from the existing code inClusterDistributionChannelWriter
(the constructor), it seems that we can't trust that theClusterClientOptions
is guaranteed to be used. I the end, I decided that some "extra" commands added inClientOptions
- with logic remaining the the channel writers was the most straightforward.