Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Linting: Update how-to-write-a-parser.md to not contain Ruff violations #12214

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

Merged
merged 1 commit into from
Apr 10, 2025

Conversation

valentijnscholten
Copy link
Member

The how-to-write-a-parser contained code that made Ruff unhappy.

Copy link

dryrunsecurity bot commented Apr 10, 2025

DryRun Security Summary

A documentation patch updates type comparison code snippets in a parser writing guide from == to is to improve type identity checking and mitigate potential type-related logic errors.

Expand for full summary

Summary: A documentation patch modifies type checking code snippets in a parser writing guide, replacing == with is for more precise type comparisons in Python.

Security Findings:
• Potential Type-Related Vulnerability Mitigation

  • Location: docs/content/en/open_source/contributing/how-to-write-a-parser.md
  • Lines 177 and 192 modified
  • Risk: Potential for type-related logic errors in type comparisons
  • Explanation: Switching from == to is provides more precise type identity checking, reducing risk of unexpected type-based behavior

No additional concrete security vulnerabilities were found in the provided summary.

View PR in the DryRun Dashboard.

@valentijnscholten valentijnscholten changed the base branch from master to bugfix April 10, 2025 19:07
Copy link
Contributor

@mtesauro mtesauro left a comment

Choose a reason for hiding this comment

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

Approved

@mtesauro mtesauro merged commit 7098998 into bugfix Apr 10, 2025
147 of 148 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants