-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Fix lint in superset/db_engine_spec
#8338
Fix lint in superset/db_engine_spec
#8338
Conversation
❤️ 👍 |
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.
LGTM
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.
Oops looks like CI unit tests are failing
Yes, it appears so - I think I just need to update a couple tests. |
bad method signature
different method naming
2f343e9
to
79f4965
Compare
OK, CI is green - sorry for the many commits. Let me know if you'd like me to squash before merge. |
We force "Squash and merge" on this repo, so every PR gets auto-squashed and we have a 1-to-1 between commits in master and PRs. |
@@ -841,47 +843,6 @@ def _process_array_data( | |||
array_value[array_child] = "" | |||
return all_array_data | |||
|
|||
@classmethod | |||
def _consolidate_array_data_into_data( |
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.
unused? @betodealmeida is this used in a cherry or something?
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.
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.
Yes, #8233 simplified the logic and left some methods that are no longer used.
* Enable lint checking for files in db_engine_spec that have few to no lint issues * Enable lint and fix issue in db_engine_spec/mysql.py * Enable pylint and fix lint for db_engine_spec/pinot.py * Enable lint and fix issues for db_engine_specs/hive.py * Enable lint and fix for db_engine_spec/presto.py * Re-enable lint on base.py, fix/disable specific failures, including one bad method signature * Make flake8 happy after a number of pylint fixes * Update db_engine_spec_test test cases related to Presto to support different method naming * automated reformatting * One more pylint disable for druid.py * Find the magic invocation that makes all the lint tools happy
CATEGORY
Choose one
SUMMARY
The
db_engine_spec
folder was largely un-linted by pylint, due to the presence of the# pylint: disable=C,R,W
comment in most of the files. This method of skipping lint checks will hide all pylint failures introduced into the files. This PR removes those lines, fixes a number of pylint errors, and uses a more targeted disable approach for issues that would require larger refactors to resolve. Using this approach for disabling lint should highlight new problems introduced in future PRs and creates a specific list of items to clean up down the road.BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TEST PLAN
ADDITIONAL INFORMATION
Explanation: there was a function in
presto.py
that I believe was un-referenced:_consolidate_array_data_into_data
.REVIEWERS