-
-
Notifications
You must be signed in to change notification settings - Fork 653
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
Rules documentation improvements #2542
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2542 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 163 163
Lines 11771 11781 +10
=========================================
+ Hits 11771 11781 +10
Continue to review full report at Codecov.
|
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.
Went a little crazy reviewing wording myself. 😄
Co-authored-by: Barry Hart <barrywhart@yahoo.com>
Co-authored-by: Barry Hart <barrywhart@yahoo.com>
Co-authored-by: Barry Hart <barrywhart@yahoo.com>
Co-authored-by: Barry Hart <barrywhart@yahoo.com>
Co-authored-by: Barry Hart <barrywhart@yahoo.com>
Co-authored-by: Barry Hart <barrywhart@yahoo.com>
Co-authored-by: Barry Hart <barrywhart@yahoo.com>
Co-authored-by: Barry Hart <barrywhart@yahoo.com>
Co-authored-by: Barry Hart <barrywhart@yahoo.com>
Thanks for the very thorough review @barrywhart ! Think I've addressed all the comments. |
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.
Looks great. Thanks for doing this!
@barrywhart I added some more changes for your old issue as noted here: #812 (comment) Mind giving those changes a quick once over in case of typos or difficult to understand phrasing? |
Ok gave this another read over and am happy with it. Gonna merge as quite a big PR so don’t like leaving those open for merge conflict hell. |
Brief summary of the change made
Fixes #2544
Fixes #812
as well as making a host of other changes.
I noticed a couple of things that bugged me with the rules documentation page, and ended up going down the rabbit hole and fixing loads of things. None of them are major, but they bug me!
I have also added a new test to check the
@document_configuration
decorator is added when there are config options because it was missing in a lot of cases.Examples of some things I have fixed in this:
Rule L001:
Issues:
•
is not code formatted.sqlfluff fix
compatible" line looks a bit odd starting with codeNew version:
Rule L004
Issues:
New version:
Rule L007
Issues:
New version:
Rule L009:
Issues - scrolling in code block
New version:
Are there any other side effects of this change that we should be aware of?
Nope, but lots of changes here!
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/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.