Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discuss / fix: custom components naming (dash, case-mixing) #248

Open
PK1A opened this issue Jul 22, 2014 · 0 comments
Open

Discuss / fix: custom components naming (dash, case-mixing) #248

PK1A opened this issue Jul 22, 2014 · 0 comments

Comments

@PK1A
Copy link
Contributor

PK1A commented Jul 22, 2014

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant