Skip to content

Fix issues with Md031 related to Issue 1364. #1371

@jackdewinter

Description

@jackdewinter

Prerequisites

  • Are you running the latest version of this application?
  • Have you checked the Frequently Asked Questions document?
  • Have you simplified the bug report to the essential details?
    • Do you have a distinct command line to report?
    • Can you clearly state the configuration for this bug report?
    • Do you have a minimal document that highlights this bug?
    • Are any required files (configuration or Markdown document) attached to the issue?
  • Did you perform a cursory search of other issues to look for related issues?

Bug Report

Bug Type

  • Fix/Rule not working as expected

Description

With [Issue 1274](MD031 fix issue) addressing parsing issues, the following Md031 fix issues were able to be addressed:

  • bad_fenced_block_in_list_in_list_with_previous_inner_block_double_drop_with_thematics
  • bad_fenced_block_in_block_quote_in_list_in_list_with_previous_block_triple_drop
  • bad_fenced_block_in_block_quote_in_list_in_list_with_previous_block_triple_drop_and_thematics
  • bad_fenced_block_in_block_quote_in_list_in_list_with_previous_list_triple_drop
  • bad_fenced_block_in_block_quote_in_list_in_list_with_previous_list_triple_drop_and_thematics
  • bad_fenced_block_in_list_in_list_in_list_with_previous_block_double_drop_with_thematics

Note that this is related to the MD031 fix issue and these parsing fix issues.

Specifics

What operating system and version are you running into this behavior on?

Win11

What version are you seeing this behavior in? (Run pip list or pipenv run pip list and look for the entry beside pymarkdownlnt.)

latest, main

Are there any extra steps that need to be taken before executing the application?

No

What is the command line you invoke to get this behavior?

See test names above.

Are you using a configuration file? Either on the command line or one of the implicit configuration files? If so, attach that file to this issue.

No.

What Markdown document causes this behavior to manifest? Attach that file to this issue.

See test names above.

Actual Behavior

In each of the above cases, the problems noted in Issue 1274 was preventing a proper fix for each of the above tests to be calculated. With those problems addressed, they could now be fixed.

Expected Behavior

All tests should pass. This includes being able to tokenize Markdown into tokens and then to rehydrate those tokens back into the original Markdown.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions