add important clarification to <template> #1283
Merged
Conversation
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
`<template>` is used as a wrapper for [conditional rendering](https://v3.vuejs.org/guide/conditional.html#conditional-groups-with-v-if-on-template) of multiple elements, and as such **is** allowed to exist multiple times within a component, even a single-file one, but the top-level `<template>` tag must be only one.
NataliaTepluhina
approved these changes
Oct 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of Problem
<template>is used as a wrapper for conditional rendering of multiple elements, and as such is allowed to exist multiple times within a component, even a single-file one, but the top-level<template>tag must be only one.Proposed Solution
By specifying that the constraint applies only to top-level instances of
<template>, the ambiguity or possible confusion with the other use of the tag is avoided. Better alternatives to "top-level" could exist, but it's the most unambiguous term I could think of.