Recursive components in Vue - Step-by-Step Execution

Concept Flow - Recursive components

Component calls itself

↓

Pass props for child

↓

Render child component

↓

Child calls itself again?

↓

Repeat steps

↓

Done

A component renders itself recursively by calling itself with new data until a base case stops recursion.

Execution Sample

Vue

<script setup>
const props = defineProps({
  node: Object
})
defineOptions({
  name: 'RecursiveComponent'
})
</script>
<template>
  <div>
    {{ node.name }}
    <div v-if="node.children">
      <RecursiveComponent
        v-for="child in node.children"
        :key="child.name"
        :node="child"
      />
    </div>
  </div>
</template>

This Vue component renders a tree node and recursively renders its children if any.

Execution Table

Step	Component Instance	Props.node.name	Condition (node.children?)	Action	Rendered Output
1	Root	Root	Yes	Render Root, call RecursiveComponent for each child	<div>Root<div>Child 1...</div><div>Child 2...</div></div>
2	Child 1	Child 1	Yes	Render Child 1, call RecursiveComponent for its child	<div>Child 1<div>Grandchild 1...</div></div>
3	Grandchild 1	Grandchild 1	No	Render Grandchild 1, no children, stop recursion	<div>Grandchild 1</div>
4	Child 2	Child 2	No	Render Child 2, no children, stop recursion	<div>Child 2</div>
5	End	-	-	All nodes rendered, recursion ends	Full nested tree rendered

💡 Recursion stops when a node has no children (base case).

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
props.node.name	Root	Root	Child 1	Grandchild 1	Child 2	-
props.node.children	[Child 1, Child 2]	[Child 1's child]	null	null	null	-
Rendered Output		<div>Root...</div>	<div>Child 1...</div>	<div>Grandchild 1</div>	<div>Child 2</div>	Full nested tree

Key Moments - 3 Insights

Why does the component call itself multiple times?

Because each node with children triggers a new RecursiveComponent instance for each child, as shown in steps 1 and 2 in the execution_table.

What stops the recursion from going forever?

When a node has no children (node.children is null or undefined), the component does not call itself again, stopping recursion as seen in steps 3 and 4.

How does Vue know to render nested children correctly?

Each recursive call receives a different props.node, so Vue renders each level separately, nesting the output inside the parent div, shown in the Rendered Output column.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What is the value of props.node.children?

A Array with children

B null

C Undefined

D Empty string

💡 Hint

Check the 'Condition (node.children?)' column at step 3 in the execution_table.

At which step does the recursion stop for a node with no children?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look for the first step where 'Condition (node.children?)' is 'No' in the execution_table.

If the root node had no children, how would the execution_table change?

A There would be more steps for children

B Steps 1 to 5 remain the same

C Only step 1 would appear with condition 'No' and recursion stops immediately

D The recursion would never stop

💡 Hint

Refer to the exit_note and the condition column in the execution_table.

Concept Snapshot

Recursive components in Vue:
- A component calls itself inside its template.
- Pass props to child instances for recursion.
- Base case: stop when no children.
- Builds nested UI like a tree.
- Useful for hierarchical data rendering.

Full Transcript

Recursive components in Vue work by a component calling itself inside its template to render nested data structures like trees. Each recursive call receives a different piece of data via props. The recursion continues until a base case is met, typically when the current node has no children. This stops further recursive calls. The execution table shows each step where the component instance renders a node and calls itself for children if present. Variable tracking shows how props.node changes at each step. Key moments clarify why recursion stops and how Vue renders nested children. The visual quiz tests understanding of recursion stopping conditions and data flow. This method helps render complex nested UI with simple reusable components.

Practice

1. What is the main purpose of a recursive component in Vue?

easy

A. To handle user input events more efficiently

B. To create multiple unrelated components in one file

C. To optimize component rendering speed by caching

D. To allow a component to call itself to render nested or hierarchical data

Solution

1. Step 1: Understand recursive component concept

   A recursive component is designed to call itself to handle nested or hierarchical data structures like trees or nested menus.

2. Step 2: Compare options with definition

   Only To allow a component to call itself to render nested or hierarchical data correctly describes this behavior. Other options describe unrelated concepts.

3. Final Answer:

   To allow a component to call itself to render nested or hierarchical data -> Option D

4. Quick Check:

   Recursive component = self-calling component [OK]

Hint: Recursive means component calls itself for nested data [OK]

Common Mistakes:

• Confusing recursion with event handling
• Thinking recursive means multiple components in one file
• Assuming recursion is about performance optimization

2. Which of the following is the correct way to name a recursive component in Vue 3 so it can call itself?

easy

A. const TreeNode = defineComponent({ components: { TreeNode }, ... })

B. const TreeNode = defineComponent({ setup() { return {}; } })

C. const TreeNode = defineComponent({ name: 'TreeNode', ... })

D. const TreeNode = defineComponent({ recursive: true, ... })

Solution

1. Step 1: Identify how to enable self-reference

   Vue requires a component to have a name property to call itself recursively by that name.

2. Step 2: Check options for correct naming

   const TreeNode = defineComponent({ name: 'TreeNode', ... }) correctly sets the name property. const TreeNode = defineComponent({ setup() { return {}; } }) lacks a name, C incorrectly tries to register itself as a child, and D uses a non-existent property.

3. Final Answer:

   const TreeNode = defineComponent({ name: 'TreeNode', ... }) -> Option C

4. Quick Check:

   Set component name for recursion [OK]

Hint: Name the component to enable self-reference [OK]

Common Mistakes:

• Omitting the name property
• Trying to register the component inside itself
• Using invalid properties like 'recursive'

3. Given this recursive component snippet, what will be rendered if node has two children?

<template>
  <div>{{ node.name }}
    <TreeNode v-for="child in node.children" :key="child.id" :node="child" />
  </div>
</template>

medium

A. The component renders the node's name and recursively renders each child node inside nested divs

B. Only the root node's name is rendered, children are ignored

C. An infinite loop occurs causing a crash

D. The component renders the node's name but children are rendered as plain text

Solution

1. Step 1: Understand recursive rendering logic

   The component renders the current node's name, then for each child, it calls itself recursively, rendering nested divs for children.

2. Step 2: Analyze output for two children

   With two children, the component renders the root node's name, then two nested TreeNode components, each rendering their own names and children recursively.

3. Final Answer:

   The component renders the node's name and recursively renders each child node inside nested divs -> Option A

4. Quick Check:

   Recursive call renders nested children [OK]

Hint: Recursive components render nested children inside themselves [OK]

Common Mistakes:

• Assuming children are ignored
• Thinking recursion causes infinite loop here
• Expecting children as plain text instead of components

4. What is the main issue with this recursive component code?

<template>
  <div>{{ node.name }}
    <TreeNode v-for="child in node.children" :node="child" />
  </div>
</template>

<script>
export default {
  name: 'TreeNode',
  props: ['node']
}
</script>

medium

A. Props are not declared correctly, should use props: { node: Object }

B. Missing :key on v-for causing rendering warnings

C. The component lacks a name property for recursion

D. Recursive call will cause infinite loop without a base case

Solution

1. Step 1: Check for common recursive component issues

   The code correctly names the component and declares props. The recursive call is valid.

2. Step 2: Identify missing key in v-for

   Vue requires a unique :key on elements inside v-for for efficient rendering. This is missing, causing warnings.

3. Final Answer:

   Missing :key on v-for causing rendering warnings -> Option B

4. Quick Check:

   Always add :key in v-for loops [OK]

Hint: Always add :key in v-for to avoid warnings [OK]

Common Mistakes:

• Thinking name property is missing
• Believing props declaration is invalid
• Assuming infinite loop without base case

5. You want to display a nested comment thread using a recursive component. Each comment may have zero or more replies. Which approach correctly prevents infinite recursion and handles empty children arrays?

hard

A. In the template, use <Comment v-for="reply in comment.replies" :key="reply.id" :comment="reply" /> and ensure comment.replies defaults to an empty array if no replies

B. Render all comments without checking children, assuming replies always exist

C. Use a v-if to stop recursion when comment.replies is undefined, but do not default to empty array

D. Avoid recursion and flatten the comment tree before rendering

Solution

1. Step 1: Understand recursion base case

   To prevent infinite recursion, the component must handle cases where there are no children by using an empty array or conditional rendering.

2. Step 2: Analyze options for best practice

   In the template, use <Comment v-for="reply in comment.replies" :key="reply.id" :comment="reply" /> and ensure comment.replies defaults to an empty array if no replies uses v-for with a key and ensures replies default to an empty array, preventing errors and infinite loops. Render all comments without checking children, assuming replies always exist ignores empty children, C risks errors without default, and A avoids recursion but is not recursive component usage.

3. Final Answer:

   Use v-for with key and default empty array for replies -> Option A

4. Quick Check:

   Default empty array stops infinite recursion [OK]

Hint: Default children to empty array to stop recursion errors [OK]

Common Mistakes:

• Not providing default empty array for children
• Assuming children always exist
• Avoiding recursion when it's the best fit