-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Quasar components inside templates using PascalCase #1601
Comments
Hi, This is simply how Vue works. No way around it... |
Actually, a component registered in PascalCase can be used in kebab-case, but the opposite is not true (see vuejs/vue#5581). I think supporting both (i.e. registering components names in PascalCase) would be a great convenience. If you allow me, I can prepare a PR. |
You need to understand that using UMD/standalone you're not taking advantage of vue-loader which compiles your templates into render functions and allow kebab-case/pascal-case conversions as needed. In UMD, you're simply writing HTML that the browser can understand, after which Vue parses the HTML DOM nodes and initialises it. Can you detail what the PR is about pls? |
Actually, I first noticed the issue on the a project managed by vue-cli, not on standalone. As I said previously, if a component is registered (either globally via As I see here, the components are registered globally by the components
We could benchmark to see which one is more performatic:
|
Interesting. Ok, will you be willing to do some tests? I'm with you 100% on this. I'm taking some time off. Just released v0.15 and I'm beat! Talk to you the following days? |
Yes, sure. But I'm busy, I'll try to prepare the PR on weekend. |
Please note that Vue docs say: |
Leave now. |
I've noticed that I can't use Quasar components on templates using PascalCase naming, even though it works with kebab-case.
The issue doesn't occur with my own custom components defined inside Quasar.
Software version
Quasar: 0.15
JsFiddle (for Quasar v0.15+ only)
https://jsfiddle.net/14frxq99/
What did you get as the error?
No component shown.
What were you expecting?
<QBtn></QBtn>
and<q-btn></q-btn>
being equivalent.The text was updated successfully, but these errors were encountered: