Why the Composition API exists in Vue - Quick Recap

Recall & Review

beginner

What problem does the Composition API solve in Vue?

It helps organize and reuse code better, especially in large components where Options API can get messy.

beginner

How does the Composition API improve code reuse compared to the Options API?

It groups related logic together in functions, making it easier to share and maintain across components.

intermediate

Why can the Options API become hard to maintain in big projects?

Because it separates code by options like data, methods, and lifecycle hooks, making related logic scattered and harder to follow.

intermediate

What is a key benefit of the Composition API for TypeScript users?

It offers better type inference and easier integration with TypeScript compared to the Options API.

beginner

How does the Composition API help with logic organization?

It allows grouping related reactive state and functions together, making components cleaner and logic easier to understand.

Why was the Composition API introduced in Vue?

A To better organize and reuse component logic

B To replace templates with JSX

C To remove reactivity from Vue

D To make Vue slower

The Composition API was introduced to help developers organize and reuse logic more easily in Vue components.

Which problem does the Options API have that the Composition API addresses?

A Scattered related code across options like data and methods

B No support for templates

C Lack of lifecycle hooks

D No support for components

The Options API separates code by options, which can scatter related logic and make maintenance harder.

How does the Composition API group code?

A By file size

B By HTML elements

C By related logic and functionality

D By CSS styles

The Composition API groups code by related logic, making it easier to understand and reuse.

What is a benefit of the Composition API for TypeScript users?

A Removes the need for types

B Better type inference and integration

C Disables reactivity

D Forces use of classes

The Composition API works well with TypeScript, providing better type support.

Which Vue API style is better for organizing complex logic?

A Neither supports logic organization

B Options API

C Both are equally bad

D Composition API

The Composition API is designed to organize complex logic better than the Options API.

Explain why the Composition API was created and how it improves Vue development.

Think about how code is grouped and reused in components.

Describe the main differences between the Options API and the Composition API in Vue.

Focus on how code is organized and maintained.

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