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

https://github.com/jackdewinter/pymarkdown/issues/945 #961

Merged
merged 4 commits into from
Jan 27, 2024

Conversation

jackdewinter
Copy link
Owner

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

PR Type: Enhancement

PR Summary: The pull request addresses the issue of inconsistent whitespace handling in markdown parsing, specifically targeting the splitting and stripping of whitespace in various markdown elements and configurations. It includes updates to the codebase to ensure that whitespace is handled consistently across different parts of the markdown parsing process.

Decision: Comment

📝 Type: 'Enhancement' - not supported yet.
  • Sourcery currently only approves 'Typo fix' PRs.
✅ Issue addressed: this change correctly addresses the issue or implements the desired feature.
No details provided.
📝 Complexity: the changes are too large or complex for Sourcery to approve.
  • Unsupported files: the diff contains files that Sourcery does not currently support during reviews.
  • Big diff: the diff is too large to approve with confidence.

General suggestions:

  • Ensure that the stripping of whitespace is handled consistently across the codebase. If the intent is to strip all kinds of whitespace, use strip() without arguments. If only specific characters are to be stripped, this should be clearly documented.
  • Review the changes to ensure that they do not introduce redundant conditions or checks that could lead to incorrect behavior, especially when dealing with empty elements in comma-separated lists.
  • Consider improving variable naming for clarity, especially when the variable's purpose is not immediately obvious from its name.

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

@jackdewinter jackdewinter merged commit 67ee195 into main Jan 27, 2024
11 checks passed
@jackdewinter jackdewinter deleted the issue-945 branch January 27, 2024 00:12
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.

1 participant