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

odd naming convention #71

Open
nlundquist opened this issue Dec 18, 2017 · 1 comment
Open

odd naming convention #71

nlundquist opened this issue Dec 18, 2017 · 1 comment

Comments

@nlundquist
Copy link

nlundquist commented Dec 18, 2017

It's seems odd that a library named done-component is centered around a tag called can-component. This results in a bit of confusion at first glance of the relationship between the can-component library & the <can-component> tag. A novice to CanJS looking at a codebase would look at the can-component docs and see no mention of such a tag.

Obviously the library name can-component was already taken, but was there a conscious decision not to make the root tag of a .component file <done-component>?

I propose we add allow .component files to have a root tag of <done-component> while still allowing <can-component> for backwards compatibility. If we did this I'd also suggest updating the docs to use <done-component> in their examples.

@matthewp
Copy link
Contributor

I agree!

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

2 participants