DOC-5375 reactive hash examples #3336
Open
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:
mvn formatter:format
target. Don’t submit any formatting related changes.DOC-5375
Reactive examples for the hash doc page. Also fixed what I think is an incorrectly-placed
REMOVE_START
in the existing strings example.Note: this is my first reactive example, so I'm not sure of the best style, etc. In particular:
block()
calls visible in some of the examples? We could hide them, but I'm wondering if it emphasises that you have to wait for a command likehset
to complete before you canhget
the values it has set.flatMap
only when there is a strict sequence of operations (like with the chain of dependenthincr
calls in the last example) rather than use it to recreate the exact sequence used in the equivalent Jedis examples.Any other suggestions or corrections would be very welcome :-)