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

Bug: false positive of warning ul-start-left in nested lists #478

Closed
arwedus opened this issue Sep 15, 2022 · 4 comments
Closed

Bug: false positive of warning ul-start-left in nested lists #478

arwedus opened this issue Sep 15, 2022 · 4 comments

Comments

@arwedus
Copy link

arwedus commented Sep 15, 2022

Problem:

With the attached markdown file and pymarkdown config, the following warnings are issued:

$ pymarkdown --config pymarkdown.json.txt scan pymarkdown_md006_false_positive_example.md 
pymarkdown_md006_false_positive_example.md:21:3: MD006: Consider starting bulleted lists at the beginning of the line (ul-start-left)
pymarkdown_md006_false_positive_example.md:22:3: MD006: Consider starting bulleted lists at the beginning of the line (ul-start-left)
pymarkdown_md006_false_positive_example.md:23:3: MD006: Consider starting bulleted lists at the beginning of the line (ul-start-left)

pymarkdown_md006_false_positive_example.md

pymarkdown.json.txt

Tested with: pymarkdownlnt==0.9.7 and the current main branch commit.

Expected result:

No warnings are issued, as the indentation of the outer unordered list item is inherited from the previous paragraph.

jackdewinter added a commit that referenced this issue Feb 10, 2023
jackdewinter added a commit that referenced this issue Feb 10, 2023
* #478 - Fixing issue.
@jackdewinter
Copy link
Owner

Good catch. This was actually a weird parsing error. Added some extra tests cases, and will be releasing soon.

@jackdewinter
Copy link
Owner

Can you retry this with the new 0.9.9 and see if it fixes this issue for you? According to what I see with the above information, this looks fixed to me.

@jackdewinter
Copy link
Owner

Have not received any information in a month or so, and it looks like it is closed here. Closing.

@arwedus
Copy link
Author

arwedus commented Mar 27, 2023

I just checked again, and the issue is solved; for the example file I provided above, as well as for my real-life design document. Thanks a lot @jackdewinter ! 👍🏼

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants