Support wildcards in triggers #2597
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
|
Several L047 tests are failing. |
Yeah, gonna go with a different, less drastic, approach here. As fixing L047 to handle this new wildcard syntax looks a bit more difficult. |
|
I see that this change makes the parse tree deeper. 👍🏽 |
…eb/sqlfluff into support-wildcard-in-expressions
tunetheweb
changed the title
Not anymore! This should all work now. |
Codecov Report
@@ Coverage Diff @@
## main #2597 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 163 163
Lines 11902 11902
=========================================
Hits 11902 11902
Continue to review full report at Codecov.
|
|
Good to review now @barrywhart |
barrywhart
approved these changes
Feb 10, 2022
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 #1831
Are there any other side effects of this change that we should be aware of?
Causes a number of other Yamls to (correctly!) now classify
*as wildcard expression so looks like more changes than it really is.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.