Add WhereCQLClauseAnalyzer strategies for Update, Delete #1557
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
improve code layout and error messages remove debugging code left in refactor tests to remove code duplication Will create an issue to further remove code dup for the where analyzer tests
amorton
approved these changes
Oct 16, 2024
Contributor
|
approved by making some changes, waiting for @Yuqi-Du to review and merge |
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.
Now OperationBuilder needs to pass StatementType to construct WhereCQLClauseAnalyzer, and regarding to different StatementType, there will be analyzerStrategy with different validation rules and warnings rules to check.
StatementTypes:
Checklist