PostCursorOptions - Support Additional Custom Options #511
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Allows passing custom (non-strongly typed in
PostCursorOptions) options forPostCursorAsync.This is a native implementation that does not handle duplicates between the strongly typed properties and the additional options. For example, if
FullCountis included in the additional options, it will appear twice in the serialized JSON—first with the strongly typed value and again with the value from the additional properties dictionary.Clarification: I personally need either that feature or the ForceOneShardAttributeValue support feature PR to support the
forceOneShardAttributeValueoption. I've created both approaches for your convenience, but both will work for me.