-
Notifications
You must be signed in to change notification settings - Fork 19
Description
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
When rehydrating the Markdown for this example, the leading spaces in the previous block quote's end token are used. In cases like this example, that end token data is not being set correctly, resulting in bad Markdown being rehydrated.
Specifics
What operating system and version are you running into this behavior on?
N/A
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?
test_extra_044mx60
What is the command line you invoke to get this behavior?
test_extra_044mx60
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.
N/A
What Markdown document causes this behavior to manifest? Attach that file to this issue.
1. > + _____
> > block 1
> > block 2
> <!--
> A code block
> -->
Actual Behavior
When this example is rehydrated, line 4 begins with a ' >' instead of a ' > '.
Expected Behavior
Proper indentation is required to properly rehydrate.