no-shadowed-elements false-positive
See original GitHub issueWe have something like:
<video class="video-js" preload="none" poster={{url model.poster}}>
{{#each subtitles as |track index|}}
<track src={{url track.id}} label={{track.name}} default={{eq index 0}}>
{{/each}}
</video>
Which gives a no-shadowed-elements
warning for the track
element which, I think, is not correct (as far as I understand what the no-shadowed-elements
rule does).
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How do I avoid shadowed variable warnings when using ...
The error comes from using the no-shadow rule instead of @typescript-eslint/no-shadow . We added the: "@typescript-eslint/no-shadow": ...
Read more >TypeParameterShadowing - Error Prone
In some cases, the type variable being declared has no relation to the type variable being shadowed. It may be appropriate to rename...
Read more >no-shadowed-variable - Rule
When set to false parameters, classes, enums and variables declared with let or const are not considered shadowed if the shadowing occurs within...
Read more >False positive example for collision detection. The shadowed ...
Download scientific diagram | False positive example for collision detection. The shadowed area is the true area swept by the extruders. from publication: ......
Read more >Distraction-Aware Shadow Detection - CVF Open Access
the detection of false positives and false negatives, achiev- ... tive distraction (FND) - shadow regions with non-shadow patterns. ... element-wise.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I would not be surprised if many more people find this difficult, therefore a little more context. Do not give your handlebars variables the same names as tags.
Rather do.
Thanks for mentioning that. I had used
i
(as an iterator / counter / index variable) and would not have thought this would be in any way related to the<i>
element.