-
-
Notifications
You must be signed in to change notification settings - Fork 750
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename test/fixtures/parser directory to test/fixtures/dialects #1585
Rename test/fixtures/parser directory to test/fixtures/dialects #1585
Conversation
Looks good so far. I see some CI checks are failing. Please ping me again when things are passing. |
Not my fault! 😁 Will wait for @alanmcruickshank to sort that out in the other PR and then update this before merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1173 files changed! This might be one of the biggest PRs yet!
All looks good to me though.
Codecov Report
@@ Coverage Diff @@
## main #1585 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 131 131
Lines 9175 9175
=========================================
Hits 9175 9175 Continue to review full report at Codecov.
|
…luff#1585) * Rename test/fixtures/parser to dialects * Rename * Revert keyword change Co-authored-by: Alan Cruickshank <alanmcruickshank@gmail.com>
Brief summary of the change made
Makes progress on #1575 by renaming
test/fixtures/parser
totest/fixtures/dialects
to more accurately reflect what these tests are and to align to the source code these are testing.Are there any other side effects of this change that we should be aware of?
Could be some merge conflicts if anyone is working on changing these files but looks quiet at the mo so good time to do it!
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:
.yml
rule test cases intest/fixtures/rules/std_rule_cases
..sql
/.yml
parser test cases intest/fixtures/parser
(note YML files can be auto generated withpython test/generate_parse_fixture_yml.py
or by runningtox
locally).test/fixtures/linter/autofix
.Added appropriate documentation for the change.
Created GitHub issues for any relevant followup/future enhancements if appropriate.