[BUG] [Linter] H012 false positive #348
Comments
heitorado
changed the title
christopherpickering
pushed a commit
that referenced
this issue
Aug 24, 2022
# [1.12.0](v1.11.1...v1.12.0) (2022-08-24) ### Bug Fixes * **h006:** prevented false positives on H006 ([215bd23](215bd23)), closes [#344](#344) [#333](#333) * **h012:** prevent H012 from matching the contents of tags or attributes ([4480cff](4480cff)), closes [#348](#348) * **t001:** fixed false positive on multiline template tags ([ea76672](ea76672)), closes [#350](#350) ### Features * **h021:** allow inline styles that contain template syntax ([f1a39ed](f1a39ed)), closes [#351](#351) * **t002:** allow variables names to be used in the {% extends tag ([a5d96e7](a5d96e7)), closes [#349](#349)
|
🎉 This issue has been resolved in version 1.12.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System Info
3.10.4)1.11.1)djangoIssue
When using HTMX or Alpine, sometimes we write a tiny bit of code inside double quotes on HTML tag attributes. These pieces of code might include the
=sign which is triggering the H012 rule.How To Reproduce
Check that these code snippets all fall into the H012 rule but none of them should.
<button x-on:click="myVariable = {{ myObj.id }}" class="text-red-600 hover:text-red-800"><span x-text="showSource == true ? 'Hide source' : 'Show source'"></span><button x-on:click="open = !open" class="flex items-center mt-2">The text was updated successfully, but these errors were encountered: