Rule request [no-unknown-html-attributes]

It’s really easy to create mistake (especially for newcomers) working with arguments/attributes in Angle components.

example

<FlashMessage flash={{flash}} />

vs

<FlashMessage @flash={{flash}} />

And it’s likely hard to debug, because it’s impossible to get list of passed to component html attributes (even in ember inspector) cc @chancancode

I wondering, is it make sence to have all list of possible attributes, and produce error if developer trying to specify invalid html attribute for Angle component?

[rwjblue]

we can start from this, and later land new attributes.

I don’t think so. This technique would mean that we start with a non-trivial number of invalid errors being flagged. That just isn’t a good trade off.

We’d also have to properly account for web components, but that seems fairly easy…

for now we can completely skip validation for web components, I thing we can start with applying this rule only for Angle components (not all nodes), and existing list of attributes should cover > 90% use-cases

See, told you it was easy 😉

[lifeart]

one more list: https://github.com/iandevlin/html-attributes