Fix template-no-arguments-for-html-elements: align HTML-element detection with upstream#2687
Open
johanrd wants to merge 1 commit intoember-cli:masterfrom
Open
Conversation
…tion with upstream Replace static htmlTags package check with inverse-of-component-detection (reject tags with : / . / uppercase / @ / -). Matches upstream's isAngleBracketComponent semantics. Custom elements are now correctly excluded.
2ff4253 to
3118f91
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
html-tagspackage check with the inverse-of-isAngleBracketComponentlogic from upstream<my-element @foo="x">) are no longer false-positively flagged:/./@/ uppercase /-are treated as plain HTML elementsTest plan
<my-element @foo="x">→ valid (custom element, not HTML)<NS.Foo @bar="baz">→ valid (namespaced component)<div @foo="x">→ still flagged