You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an issue based on the comment in #245. The basic problem here is a fundamental mismatch between HTML syntax for tags / attributes and JS syntax for variables / object properties:
HTML - case-insensitive, doesn't allow spaces, allow dashes in names
JS - case-sensitive, one has great flexibility in naming properties of objects, somehow more restricted in naming variables.
Since the custom components are JavaScript variables / object properties and custom component invocation look a lot like HTML tags we need to makes those 2 worlds to co-exist somehow.
The particular issue to be fixed in this issue is to allow components with a dash in their name (ex.: <#foo-bar />) but I think a more general thought about naming of custom components and their attributes would be in order.
The text was updated successfully, but these errors were encountered:
This is an issue based on the comment in #245. The basic problem here is a fundamental mismatch between HTML syntax for tags / attributes and JS syntax for variables / object properties:
HTML - case-insensitive, doesn't allow spaces, allow dashes in names
JS - case-sensitive, one has great flexibility in naming properties of objects, somehow more restricted in naming variables.
Since the custom components are JavaScript variables / object properties and custom component invocation look a lot like HTML tags we need to makes those 2 worlds to co-exist somehow.
The particular issue to be fixed in this issue is to allow components with a dash in their name (ex.:
<#foo-bar />
) but I think a more general thought about naming of custom components and their attributes would be in order.The text was updated successfully, but these errors were encountered: