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

Markdown lint not working #3147

Closed
judsoniv opened this issue Jul 24, 2019 · 5 comments
Closed

Markdown lint not working #3147

judsoniv opened this issue Jul 24, 2019 · 5 comments
Labels
bug 🐛 Issue concerns a bug. level 1 ❕ A bug that caused minor damage: App is still usable, but minor features might not work.

Comments

@judsoniv
Copy link

judsoniv commented Jul 24, 2019

Current behavior

Beginning in v0.12.0, the Markdown lint feature no longer works.

The configurations are still present, as is the configuration-options box introduced in the previous release. However, making a syntax error in your markdown to longer results in a "warning" marker in the margin.

I've attempted toggling the feature, turning on line numbers, etc., to no avail.

Expected behavior

Return to the previous behavior. Making a syntax error in your markdown should result in an interface warning, unless turned off in your configuration settings.

Steps to reproduce

  1. Turn on linting
  2. Make a mistake, such as starting your document with an H2 rather than an H1
  3. Be saddened by the lack of a lint warning

Environment

  • Version : 0.12.0
  • OS Version and name : Mac OS 10.14.5
@Flexo013
Copy link
Contributor

Confirmed this issue on Windows 10.

@Flexo013 Flexo013 added bug 🐛 Issue concerns a bug. level 1 ❕ A bug that caused minor damage: App is still usable, but minor features might not work. labels Jul 25, 2019
@Flexo013 Flexo013 changed the title Markdown lint broken in latest 0.12.0 Markdown lint broken in 0.12.0 Jul 25, 2019
@Flexo013 Flexo013 changed the title Markdown lint broken in 0.12.0 Markdown lint not working Jul 27, 2019
@Flexo013
Copy link
Contributor

Confirmed for 0.12.1

@judsoniv
Copy link
Author

Confirmed for 0.13.0

I am sad.

@Flexo013
Copy link
Contributor

@roottool Could you look into this, since you were the one who added the feature?

@ZeroX-DG
Copy link
Member

Fixed: #3285

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Issue concerns a bug. level 1 ❕ A bug that caused minor damage: App is still usable, but minor features might not work.
Projects
None yet
Development

No branches or pull requests

3 participants