We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If I have the following haml, I expect haml-lint to give me an ImplicitDiv warning, which it currently does.
ImplicitDiv
%div.supervisor-page
However if I have the following haml, I would expect it to not raise an ImplicitDiv warning.
%div{id: leaderboard.code}
Yet it does, and the suggestion that it offers isn't quite right either.
[W] ImplicitDiv: `%div` can be written as `.code}` since `%div` is implicit
It seems to think that my method call anywhere after %div is supposed to be the class that I'm using on the div.
%div
The text was updated successfully, but these errors were encountered:
👍
Sorry, something went wrong.
Fixed by @hackling in #34. Thanks for the report!
yay!
I'm also getting a false positive with an email view since I had to style it inline:
%div{ style: 'width: 600px; padding: 40px; margin: 0 auto; background-color: #282f36;' }
Getting:
`%div` can be written as `#282f36;'` since `%div` is implicit
Appreciate all the hard work!
Successfully merging a pull request may close this issue.
If I have the following haml, I expect haml-lint to give me an
ImplicitDiv
warning, which it currently does.However if I have the following haml, I would expect it to not raise an
ImplicitDiv
warning.%div{id: leaderboard.code}
Yet it does, and the suggestion that it offers isn't quite right either.
It seems to think that my method call anywhere after
%div
is supposed to be the class that I'm using on the div.The text was updated successfully, but these errors were encountered: