BigQuery: Basic FOR..IN..DO...END FOR support
#3340
Merged
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## main #3340 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 168 168
Lines 12724 12740 +16
=========================================
+ Hits 12724 12740 +16
Continue to review full report at Codecov.
|
| """Overriding StatementSegment to allow for additional segment parsing.""" | ||
|
|
||
| type = "multi_statement_segment" | ||
| match_grammar: Matchable = OneOf( |
There was a problem hiding this comment.
Future proofing!
There's some more multi-statemnt control statements we should add here (WHILE...DO...END WHILE...etc) that I intend to add here, if this PR is approved. Did consider adding to this PR but then decided to get this approved first and then build upon it.
3 tasks
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.
Brief summary of the change made
Fixes #3316
This could also for the basis of other Procedure Syntax
Are there any other side effects of this change that we should be aware of?
At the moment this is only top level basic support, so doesn't included nested statements.
Pull Request checklist
Please confirm you have completed any of the necessary steps below.
Included test cases to demonstrate any code changes, which may be one or more of the following:
.ymlrule test cases intest/fixtures/rules/std_rule_cases..sql/.ymlparser test cases intest/fixtures/dialects(note YML files can be auto generated withtox -e generate-fixture-yml).test/fixtures/linter/autofix.Added appropriate documentation for the change.
Created GitHub issues for any relevant followup/future enhancements if appropriate.