Loosen restrictions around component argument names about rfcs HOT 6 OPEN

Wellllll, actually we might want to go the other direction. @dfreeman discovered some non-trivial issues with allowing div and friends as legal names in the context of what Glint needs to do, and notably Svelte and Vue have restrictions on names for the same reasons. I think Dan was planning to write up a related RFC; I suspect he would also be up for supporting/helping Bert doing the same.

from rfcs.

@bertdeblock happy to sync with you out-of-band (via Discord or whatever works for you) to work together on figuring out how this relates to the issues Chris mentioned above and whether it makes sense to join forces 🙂

from rfcs.

The current naming convention is also not fully enforced. You can set an argument starting with an underscore using {{component _foo="bar"}} helper. You can not access it using the {{@_foo}}. But you can access it using {{this.args._foo}}`. 🤯 Using this in production at Ember Bootstrap. 🙈

from rfcs.

Both cases make sense to me, esp. the capital-case component name (@Wrapper={{component 'my-component'}}) is something I've personally ran into multiple times.

from rfcs.

This is also directly related to the fact that there is no syntactical restriction on component invocation in strict mode templates—basically by definition: if the name from the surrounding JS scope is available to invoke, then any legitimate JS identifier needs to be invokable. That means that <foo /> can be a legal component invocation, and passing @Foo={{bar}} should also.

from rfcs.

@chriskrycho what would an RFC for this look like? Are you able to give any pointers to @bertdeblock ?

from rfcs.