-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Update built-in-components.md. Rename <teleport> to <Teleport> #2497
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion: according to styleguide, self-closing component tags can be capitalized, while opening/closing tags should be lowercase. Let's keep the fixes above and remove this one
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@NataliaTepluhina big thanks for reviewing this request.
Sorry, I know that you know Vue better, but I did not see this line in the your link :/
I just see:
" In most projects, component names should always be PascalCase in Single-File Components and string templates - but kebab-case in in-DOM templates."
Also lowercase is used to distinguish built-in elements such as slot and template
https://vuejs.org/api/built-in-special-elements.html#component
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FreshHead here is a relevant screenshot:
So for self-closing components we prefer the Pascal case, for opening/closing tags we prefer kebab-case
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@NataliaTepluhina, I am confused. I read it like: "In Single-File Components use PascalCase and kebab in in-DOM templates". Not self-enclosings components should be capitalized and components with content in slot should be lowercased.
For me code snippet bellow can easily be used in SFC:
It is even more confusing that in the teleport doc page Teleport component is always capitalized: https://vuejs.org/guide/built-ins/teleport.html#basic-usage

And for me lowercasing Teleport component is clashed with convention to distinguish special elements and components:
https://vuejs.org/api/built-in-special-elements.html#component