-
-
Notifications
You must be signed in to change notification settings - Fork 699
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
L031 - Avoid using aliases in join coditions #473
L031 - Avoid using aliases in join coditions #473
Conversation
bf28fe5
to
9689b86
Compare
Hi @piotrgredowski , thanks for getting involved. A few tips on your approach:
|
ef1cec3
to
e1b16be
Compare
Codecov Report
@@ Coverage Diff @@
## master #473 +/- ##
==========================================
+ Coverage 92.62% 92.70% +0.07%
==========================================
Files 29 29
Lines 4708 4754 +46
==========================================
+ Hits 4361 4407 +46
Misses 347 347
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
This is very dirty version, returning too many edit: nevermind. I've found tests for |
268173d
to
f89f5a1
Compare
Add LintFix for L031
f89f5a1
to
09bfe2e
Compare
I've added support for self-joins too. |
Hey @piotrgredowski this is really cool, nice job with the fix implementation too. I'm going to approve but defer to @alanmcruickshank to merge as he had a few questions above (which I'm 99% sure you've addressed). |
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.
Thank you!
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.
Thanks for this @piotrgredowski ! Very neat PR, good work on the fix, excellent test coverage. 👍
I've got a broader question about whether we should also have a rule against initialisms in aliases for tables in a FROM
clause. I think that's a vagueness in the fishtown style guide rather than a problem with the work you've done though. I'll raise a separate issue for it.
This is just a WIP PR for #469
Just wanted to ask if it is good approach to solve presented problem :)
There is a lot to improve - especially docstrings, SQL file name etc. But yeah. It's just a start :)