Skip to content
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

cleanup: add pre-commit + resolve pylint warnings #210

Merged
merged 4 commits into from
Jul 13, 2023

Conversation

korikuzma
Copy link
Contributor

See #139 and #149

* Resolved easy pylint warnings
* For those that had `too-many` warnings, I just disabled
* Disable `fixme` for pylint
* Name changes for variable names / imports
@korikuzma korikuzma requested a review from a team as a code owner July 11, 2023 14:43
@korikuzma korikuzma self-assigned this Jul 11, 2023
@korikuzma korikuzma requested a review from a team as a code owner July 11, 2023 14:43
Copy link
Contributor

@jsstevenson jsstevenson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally I would be 👍 for blanket ignoring "too few public methods" and "too many locals" in pylintrc

@korikuzma
Copy link
Contributor Author

@jsstevenson We have #153 . Did we want to completely ignore or up the max that we'd allow? I'm fine with either

@jsstevenson
Copy link
Contributor

jsstevenson commented Jul 12, 2023

@korikuzma in my opinion (having thought about it for maybe... 90 seconds?), I think "too few public methods" just isn't a useful check for this codebase, and personally I'd be happy to blanket-ignore it.

I looked again at the "too many locals" example and I think it's fine to leave it at the default value for now. It'd be nice to go through en masse (maybe at a future hackathon or during a free week) and try to make refactors to really resolve these issues rather than just ignoring them.

@korikuzma korikuzma merged commit eb34da7 into 0.9 Jul 13, 2023
@korikuzma korikuzma deleted the issue-139-metaschema branch July 13, 2023 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants