Closed jackdewinter closed 1 month ago
This pull request addresses issue #1217 by fixing an issue with nested list starts not being accounted for properly in the pymarkdown project. The changes primarily affect the handling of fenced code blocks within nested lists and the calculation of line number deltas in the LeadingSpaceIndexTracker class.
No sequence diagrams generated as the changes look simple and do not need a visual representation.
Change | Details | Files |
---|---|---|
Added new test cases for fenced code blocks within nested lists |
|
test/test_markdown_extra.py test/rules/test_md031.py |
Modified LeadingSpaceIndexTracker class to handle nested list starts correctly |
|
pymarkdown/plugins/utils/leading_space_index_tracker.py |
Updated project metadata and documentation |
|
publish/coverage.json publish/test-results.json newdocs/src/changelog.md |
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 100.00%. Comparing base (
e479453
) to head (41eb15a
). Report is 1 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
closes #1217
Summary by Sourcery
Fix nested list parsing issue and enhance test coverage with new test cases for bad fenced blocks in nested lists. Refactor code to simplify method parameters and update the changelog with the latest bug fix.
Bug Fixes:
Enhancements:
__process_container_end_block_quote
method to remove theend_tokens
parameter and use the class attribute instead.Documentation:
Tests: