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

Suppress unused-argument for functions in migration modules #273

Merged
merged 1 commit into from
Jul 22, 2020

Conversation

atodorov
Copy link
Contributor

usually these are functions used in migrations.RunPython() but
the suppression code is not that smart and will suppress any
unused-argument which is triggered by functions defined inside a
migrations module.

@carlio I've started using the new pylint_django.checkers.migrations in my own projects and started hitting this. What do you think ?

@atodorov atodorov requested a review from carlio July 20, 2020 10:08
@atodorov atodorov force-pushed the migrations_unused_arguments branch from 2575ef6 to 39d792b Compare July 20, 2020 10:16
@coveralls
Copy link

coveralls commented Jul 20, 2020

Pull Request Test Coverage Report for Build 1130

  • 4 of 4 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.06%) to 88.462%

Totals Coverage Status
Change from base Build 1115: 0.06%
Covered Lines: 667
Relevant Lines: 754

💛 - Coveralls

usually these are functions used in migrations.RunPython() but
the suppression code is not that smart and will suppress any
unused-argument which is triggered by functions defined inside a
migrations module.
@atodorov atodorov force-pushed the migrations_unused_arguments branch from 39d792b to 704e93c Compare July 20, 2020 12:32
@atodorov atodorov merged commit 502125c into master Jul 22, 2020
@atodorov atodorov deleted the migrations_unused_arguments branch July 22, 2020 09:24
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