Why component patterns matter in Vue - See It in Action

Why component patterns matter

📖 Scenario: You are building a simple Vue app to display a list of favorite fruits. You want to organize your code well so it is easy to read and reuse.

🎯 Goal: Create a Vue 3 component that shows a list of fruits using a clear pattern for components. This will help you understand why using component patterns matters for clean and maintainable code.

📋 What You'll Learn

Create a list of fruits as an array

Create a config variable to hold the title text

Use a FruitList component to render the fruits

Add a final template wrapper with semantic HTML

💡 Why This Matters

🌍 Real World

Organizing UI into components is how real Vue apps stay manageable as they grow.

💼 Career

Understanding component patterns is essential for frontend developer roles working with Vue or similar frameworks.

1

Create the fruits data array

Create a fruits array with these exact values: 'Apple', 'Banana', 'Cherry' inside the <script setup> block.

Vue

// Create the fruits array here
// Your code here



  

Hint

Use const fruits = ['Apple', 'Banana', 'Cherry'] inside the <script setup> block.

2

Add a title config variable

Add a title variable with the exact string value 'My Favorite Fruits' inside the <script setup> block below the fruits array.

Vue

const fruits = ['Apple', 'Banana', 'Cherry']
// Add the title variable here
// Your code here



  

Hint

Write const title = 'My Favorite Fruits' below the fruits array.

3

Create the FruitList component

Create a new component called FruitList inside the same file using <script setup> syntax. It should accept a fruits prop and render an unordered list <ul> with each fruit as a list item <li>. Use v-for with fruit and index as iterator variables.

Vue

const fruits = ['Apple', 'Banana', 'Cherry']
const title = 'My Favorite Fruits'

// Define FruitList component here
// Your code here



  

Hint

Use defineComponent with a fruits prop and return a <ul> with <li> items using map.

4

Use FruitList component in template

In the <template>, add a <section> with a heading <h1> showing the title variable. Below it, use the <FruitList> component passing the fruits array as a prop.

Vue

Hint

Wrap the content in a <section>. Use <h1>{{ title }} and then <FruitList :fruits="fruits" />.

Practice

1. Why is it important to use component patterns in Vue applications?

easy

A. They slow down the app performance

B. They make code easier to read and reuse

C. They increase the file size unnecessarily

D. They prevent the use of props

Solution

1. Step 1: Understand the role of component patterns

   Component patterns organize code into reusable parts, making it easier to manage.

2. Step 2: Identify the benefit of reusability and readability

   Using patterns helps developers read and reuse code efficiently, improving teamwork and maintenance.

3. Final Answer:

   They make code easier to read and reuse -> Option B

4. Quick Check:

   Component patterns = easier code reuse [OK]

Hint: Think about how patterns help reuse code [OK]

Common Mistakes:

• Confusing patterns with performance issues
• Assuming patterns increase file size
• Believing patterns restrict props usage

2. Which of the following is the correct way to define a simple Vue component using the Composition API?

easy

A. export default { setup: () => { count: 0 } }

B. export default function setup() { return { count: 0 } }

C. export default { setup() { return { count: 0 } } }

D. export default { data() { return { count: 0 } } }

Solution

1. Step 1: Recall Composition API syntax

   The setup() function is defined inside the component object and returns reactive state.

2. Step 2: Check each option's syntax

   export default { setup() { return { count: 0 } } } correctly defines setup() returning an object. export default function setup() { return { count: 0 } } is invalid syntax. export default { data() { return { count: 0 } } } uses Options API, not Composition API. export default { setup: () => { count: 0 } } has incorrect arrow function syntax.

3. Final Answer:

   export default { setup() { return { count: 0 } } } -> Option C

4. Quick Check:

   Correct setup() syntax = export default { setup() { return { count: 0 } } } [OK]

Hint: Remember setup() returns state object in Composition API [OK]

Common Mistakes:

• Confusing Options API with Composition API syntax
• Using arrow functions incorrectly in setup
• Not returning an object from setup

3. Given this Vue component code using a pattern for props and emits:

export default {
  props: { count: Number },
  emits: ['increment'],
  setup(props, { emit }) {
    function add() { emit('increment') }
    return { add }
  }
}

What happens when the add function is called?

medium

A. It emits an 'increment' event to the parent component

B. It changes the value of the count prop directly

C. It throws an error because emit is undefined

D. It updates the local count state automatically

Solution

1. Step 1: Understand the emit function in setup()

   The emit function sends events from child to parent components in Vue.

2. Step 2: Analyze the add() function behavior

   Calling add() triggers emit('increment'), which sends the 'increment' event upward.

3. Final Answer:

   It emits an 'increment' event to the parent component -> Option A

4. Quick Check:

   emit('increment') sends event [OK]

Hint: emit() sends events to parent components [OK]

Common Mistakes:

• Thinking props can be changed directly
• Assuming emit is undefined in setup
• Believing local state updates automatically

4. This Vue component code has an error:

import { ref } from 'vue';
export default {
  setup() {
    const count = ref(0)
    function increment() {
      count++
    }
    return { count, increment }
  }
}

What is the error and how to fix it?

medium

A. increment should be an arrow function

B. ref is not imported, so import it from 'vue'

C. setup must return a function, not an object

D. count is a ref, so use count.value++ instead of count++

Solution

1. Step 1: Identify how to update a ref value

   Refs hold values inside .value property, so count++ is invalid.

2. Step 2: Correct the increment function

   Use count.value++ to update the reactive ref correctly.

3. Final Answer:

   count is a ref, so use count.value++ instead of count++ -> Option D

4. Quick Check:

   Update ref with .value [OK]

Hint: Update ref values with .value [OK]

Common Mistakes:

• Trying to increment ref directly
• Forgetting to import ref (though not asked here)
• Thinking setup returns a function

5. You want to create a reusable Vue component pattern that accepts a list of items and emits an event when an item is selected. Which pattern best supports this goal?

hard

A. Use props to pass the list and emits to notify selection

B. Use local data to store the list and watch to detect selection

C. Use global variables to share the list and methods to select

D. Use slots to pass the list and computed properties to emit

Solution

1. Step 1: Identify how to pass data into components

   Props are the standard way to pass data like lists into Vue components.

2. Step 2: Identify how to notify parent components

   Emits are used to send events like item selection back to the parent.

3. Step 3: Evaluate other options

   Local data won't receive external lists. Global variables break encapsulation. Slots are for content, not data lists. Computed properties don't emit events.

4. Final Answer:

   Use props to pass the list and emits to notify selection -> Option A

5. Quick Check:

   Props in, emits out = reusable pattern [OK]

Hint: Props in, emits out for reusable components [OK]

Common Mistakes:

• Using local data instead of props for input
• Relying on global variables for data sharing
• Misusing slots for data passing