You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In jaraco/zipp#125, I learned that users can, intentionally or not, sneak non-printable characters into the code through otherwise innocuous pull requests. This particular one was caught by mach lint in a downstream system. It would be nice if ruff could catch such changes. I'm not confident it's possible, but I wanted to flag it as a feature for consideration.
The text was updated successfully, but these errors were encountered:
AlexWaygood
changed the title
Fature: Check for unintended non-printing characters
Feature: Check for unintended non-printing characters
Sep 10, 2024
I'm rather surprised that we don't already have that. There's an existing rule to catch ambiguous unicode characters, but it doesn't cover invisible characters.
I'm very much in favor of adding the rule. We would have to think about if it should be a new rule or be added to the above mentioned rule
@MichaReiser I agree this is a separate request, but it's related because it would be confusing if Ruff reports an invisible character without helping the user fix it. If you agree, I'll go ahead and create a new issue to track this requirement.
In jaraco/zipp#125, I learned that users can, intentionally or not, sneak non-printable characters into the code through otherwise innocuous pull requests. This particular one was caught by
mach lint
in a downstream system. It would be nice if ruff could catch such changes. I'm not confident it's possible, but I wanted to flag it as a feature for consideration.The text was updated successfully, but these errors were encountered: