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
Copy file name to clipboardExpand all lines: src/v2/guide/components.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -962,9 +962,11 @@ When registering components (or props), you can use kebab-case, camelCase, or Ti
962
962
```js
963
963
// in a component definition
964
964
components: {
965
-
// register using camelCase
965
+
// register using kebab-case
966
966
'kebab-cased-component': { /* ... */ },
967
+
// register using camelCase
967
968
'camelCasedComponent': { /* ... */ },
969
+
// register using TitleCase
968
970
'TitleCasedComponent': { /* ... */ }
969
971
}
970
972
```
@@ -978,7 +980,7 @@ Within HTML templates though, you have to use the kebab-case equivalents:
978
980
<title-cased-component></title-cased-component>
979
981
```
980
982
981
-
When using _string_ templates however, we're not bound by HTML's case-insensitive restrictions. That means even in the template, you reference your components and props using camelCase, PascalCase, or kebab-case:
983
+
When using _string_ templates however, we're not bound by HTML's case-insensitive restrictions. That means even in the template, you reference your components and props using camelCase, TitleCase, or kebab-case:
982
984
983
985
```html
984
986
<!-- use whatever you want in string templates! -->
0 commit comments