Skip to content

[use-implicit-booleaness] Fix comparison to empty strings across the codebase #7722

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

Conversation

Pierre-Sassoulas
Copy link
Member

Type of Changes

Type
🔨 Refactoring

Description

Refactor prior to #6870 where compare-to-empty-string will become a default check integrated in use-implicit-booleaness and will start to be enforced. It will be easier to review if we separate the two. Similar to #7721

…codebase

As it will become a default check in pylint-dev#6870 it will be easier to review it if we separate the two
@github-actions
Copy link
Contributor

github-actions bot commented Nov 6, 2022

🤖 According to the primer, this change has no effect on the checked open source code. 🤖🎉

This comment was generated for commit 7dfbbd3

@Pierre-Sassoulas Pierre-Sassoulas added Maintenance Discussion or action around maintaining pylint or the dev workflow Skip news 🔇 This change does not require a changelog entry labels Nov 6, 2022
@coveralls
Copy link

Pull Request Test Coverage Report for Build 3403656884

  • 6 of 6 (100.0%) changed or added relevant lines in 4 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.0005%) to 95.38%

Totals Coverage Status
Change from base Build 3401220436: -0.0005%
Covered Lines: 17240
Relevant Lines: 18075

💛 - Coveralls

@Pierre-Sassoulas Pierre-Sassoulas merged commit a04f641 into pylint-dev:main Nov 7, 2022
@Pierre-Sassoulas Pierre-Sassoulas deleted the fix-compare-to-empty-string-existing-issue branch November 7, 2022 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Discussion or action around maintaining pylint or the dev workflow Skip news 🔇 This change does not require a changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants