-
-
Notifications
You must be signed in to change notification settings - Fork 100
HAML linter is removing 1-line %div
tags, resulting in broken syntax
#1258
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
HAML linter is removing 1-line %div
tags, resulting in broken syntax
#1258
Comments
HAML is a part of this project through https://github.com/ruby-syntax-tree/syntax_tree-haml. prettier/plugin-haml is not a maintained piece of this. haml-lint doesn't have anythign to do with this project. What exactly do you have installed on your machine, and how are you running it? |
%div
tags, resulting in broken syntax
Ah! Silly me - I should have been able to figure that out. Thank you for clarifying. I updated the issue description with proper metadata. Everything seems to work great, except for the issue I describe above. Note that this is left untouched, though:
so at least I have a workaround, but would be great if this could be fixed so
would be left alone. BTW, while I'm here, is there a rule that controls whether to put a space on the inside of curly braces? |
Okay this got fixed by the version 1.2.1 of As for your other question: there aren't really "rules" per-se in this project. It's not a linter, so it doesn't treat them that way. It's just a formatter, so it formats the same way every time regardless of what the input was. |
Metadata
Input
Current output
Expected output
Current output isn't valid HAML because there's a space at the beginning. (And, also, it shouldn't remove a div.)
So I went over to https://github.com/prettier/plugin-haml to create an issue and found that the project has been archived.EDIT: I'm silly. Should have seen that that wasn't related to this project.The text was updated successfully, but these errors were encountered: