Use new IDL package for query consistency level changes #6791
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
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 changed?
cadence-idlhas been updated to support specifying QueryConsistencyLevel on theGetWorkflowExecutionHistoryandDescribeWorkflowrpcs. This PR pulls in those changes and adds support for the new fields to the mapper functions for thrift and proto.Why?
This finishes piping data from a request through to the implementation to support specifying a queryconsistencylevel in the frontend. Client updates are still required for consumers to use the fields.
How did you test it?
Updated unit tests to validate the mapper functions.
Potential risks
N/A
Release notes
N/A
Documentation Changes
N/A