Why the Composition API exists in Vue - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why was the Composition API introduced in Vue 3?

Which of the following best explains the main reason Vue introduced the Composition API?

A To force developers to write class-based components instead of functions.

B To make Vue components run faster by removing reactivity.

C To allow better code organization and reuse by grouping related logic together.

D To replace the Options API because it was deprecated and no longer supported.

💡 Hint

Think about how developers manage complex logic in components.

The Composition API was introduced to help developers organize and reuse code better by grouping related logic together, especially in complex components.

❓ component_behavior

intermediate

How does the Composition API improve code reuse?

Given two Vue components using the Composition API, what is the main way they share logic?

A By copying and pasting the entire setup function code between components.

B By extracting reusable functions called composables that return reactive state and methods.

C By using global variables to share data across components.

D By defining all logic inside the template section.

💡 Hint

Think about how functions can return reactive data to be reused.

Composables are functions that encapsulate reactive state and logic, allowing multiple components to reuse the same code easily.

📝 Syntax

advanced

Identify the correct Composition API setup syntax

Which option shows the correct way to define reactive state and a method inside the setup function using the Composition API?

Vue

import { ref } from 'vue';

export default {
  setup() {
    // define count and increment
  }
}

A

const count = ref(0);
function increment() { count.value++; }
return { count, increment };

B

const count = ref(0);
function increment() { count++; }
return { count, increment };

C

const count = reactive(0);
function increment() { count++; }
return { count, increment };

D

const count = 0;
function increment() { count++; }
return { count, increment };

💡 Hint

Remember how to create reactive variables and update their values.

Using ref creates a reactive variable. You must update its value with count.value++. Returning these allows template access.

🔧 Debug

advanced

Why does this Composition API code cause an error?

What error will this Vue 3 Composition API code cause and why? import { ref } from 'vue'; export default { setup() { const count = ref(0); function increment() { count++; } return { count, increment }; } }

A No error; the code runs correctly and increments count.

B SyntaxError because the function increment is missing parentheses.

C ReferenceError because count is not defined inside increment.

D TypeError because count is a ref object and cannot be incremented directly.

💡 Hint

Think about how to update a ref's value properly.

count is a ref object. You must update count.value, not count directly. Using count++ causes a TypeError.

❓ lifecycle

expert

How does the Composition API handle lifecycle hooks differently?

In Vue 3 Composition API, how do you register a lifecycle hook like mounted inside the setup function?

A By importing the hook function (e.g., onMounted) and calling it inside setup with a callback.

B By defining a mounted() method inside the component options object.

C By adding a mounted property to the reactive state object.

D By calling the lifecycle hook outside the setup function.

💡 Hint

Think about how Composition API uses functions to register hooks.

Composition API uses functions like onMounted imported from Vue. You call them inside setup with a callback to run code on mount.

Practice

1. Why was the Composition API introduced in Vue?

easy

A. To remove support for reactive data

B. To replace templates with plain JavaScript

C. To organize component logic by grouping related code

D. To make Vue incompatible with TypeScript

Solution

1. Step 1: Understand Vue component logic challenges

   Before Composition API, logic was scattered in options like data, methods, computed, making reuse and reading harder.

2. Step 2: Identify Composition API purpose

   The Composition API groups related logic together, improving readability and reuse.

3. Final Answer:

   To organize component logic by grouping related code -> Option C

4. Quick Check:

   Composition API = Organize logic [OK]

Hint: Composition API groups related code for clarity [OK]

Common Mistakes:

• Thinking it removes templates
• Believing it disables reactivity
• Assuming it breaks TypeScript support

2. Which of the following is the correct way to import the ref function from Vue's Composition API?

easy

A. import ref from 'vue';

B. import { ref } from 'vue';

C. const ref = require('vue');

D. import { Ref } from 'vue';

Solution

1. Step 1: Recall ES module import syntax in Vue 3+

   Vue exports Composition API functions as named exports, so use curly braces for import.

2. Step 2: Check each option

   import { ref } from 'vue'; uses named import correctly. import ref from 'vue'; tries default import which is wrong. const ref = require('vue'); uses CommonJS require which is outdated. import { Ref } from 'vue'; imports 'Ref' (capitalized) which is a type, not a function.

3. Final Answer:

   import { ref } from 'vue'; -> Option B

4. Quick Check:

   Named import with curly braces = import { ref } from 'vue'; [OK]

Hint: Use curly braces for named imports from Vue [OK]

Common Mistakes:

• Using default import instead of named import
• Using require() instead of import
• Confusing types with functions

3. What will be the output of this Vue Composition API code snippet inside a component's setup()?

import { ref } from 'vue';
export default {
  setup() {
    const count = ref(0);
    count.value++;
    return { count };
  }
}

What is the value of count when rendered?

medium

A. 0

B. An error occurs

C. undefined

D. 1

Solution

1. Step 1: Understand ref and its value property

   The ref(0) creates a reactive object with initial value 0 accessible via count.value.

2. Step 2: Analyze the increment operation

   count.value++ increases the value from 0 to 1 before returning it.

3. Final Answer:

   1 -> Option D

4. Quick Check:

   ref value incremented once = 1 [OK]

Hint: Remember to access .value with ref to get or set data [OK]

Common Mistakes:

• Expecting count to be 0 without increment
• Trying to use count directly without .value
• Thinking ref returns a primitive, not an object

4. Identify the error in this Composition API code snippet:

import { reactive } from 'vue';
export default {
  setup() {
    const state = reactive({ count: 0 });
    function increment() {
      state.count += 1
    }
    return { state, increment };
  }
}

medium

A. No error; code works correctly

B. Reactive object properties should not be mutated directly

C. Reactive must be imported as ref

D. Missing semicolon after increment function

Solution

1. Step 1: Review reactive usage

   The reactive function creates a reactive object whose properties can be mutated directly.

2. Step 2: Check the increment function

   The function increments state.count correctly without syntax errors.

3. Final Answer:

   No error; code works correctly -> Option A

4. Quick Check:

   Reactive objects allow direct property mutation [OK]

Hint: Reactive objects allow direct property changes [OK]

Common Mistakes:

• Thinking reactive properties are immutable
• Confusing reactive with ref usage
• Assuming missing semicolon causes error

5. You want to reuse a piece of logic that tracks a user's online status across multiple components. How does the Composition API help achieve this compared to the Options API?

hard

A. By allowing you to write a reusable function that returns reactive state and methods

B. By forcing you to duplicate the same data and methods in each component

C. By requiring you to use global variables for shared state

D. By removing support for reactive data in reusable code

Solution

1. Step 1: Understand logic reuse challenges in Options API

   Options API scatters logic in component options, making reuse hard without mixins or plugins.

2. Step 2: Recognize Composition API's reusable functions

   Composition API lets you write functions (composables) that return reactive state and methods to share logic easily.

3. Final Answer:

   By allowing you to write a reusable function that returns reactive state and methods -> Option A

4. Quick Check:

   Composition API enables reusable logic functions [OK]

Hint: Use composable functions to share reactive logic [OK]

Common Mistakes:

• Thinking duplication is necessary
• Believing global variables are required
• Assuming reactive data can't be reused