Composable naming conventions (use prefix) in Vue - Step-by-Step Execution

Concept Flow - Composable naming conventions (use prefix)

Create composable function

↓

Add prefix 'use' to name

↓

Export composable

↓

Import composable in component

↓

Call composable to get reactive data

↓

Use reactive data in template

This flow shows how to create a composable function with a 'use' prefix, export it, import it in a Vue component, and use its reactive data.

Execution Sample

Vue

import { ref } from 'vue'

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

Defines a composable named 'useCounter' that provides a reactive count and an increment function.

Execution Table

Step	Action	Name Used	Result	Notes
1	Define composable function	useCounter	Function created	Prefix 'use' signals composable
2	Inside composable, create reactive state	count	Ref with initial 0	Reactive state ready
3	Define increment function	increment	Function increments count	Updates reactive state
4	Return reactive state and function	count, increment	Returned as object	Composable API exposed
5	Import composable in component	useCounter	Composable imported	Ready to use in component
6	Call composable in setup()	useCounter()	Get count and increment	Reactive data available
7	Use count in template	count	Displays current count	Reactive updates reflected
8	Call increment on event	increment()	count.value increases	UI updates automatically
9	Exit	N/A	Composable used successfully	Naming convention helps clarity

💡 Composable usage ends after reactive data is used and updated in component

Variable Tracker

Variable	Start	After 1	After 2	Final
count.value	0	0	0	2
increment	function	function	function	function

Key Moments - 3 Insights

Why do we prefix composable functions with 'use'?

The 'use' prefix clearly identifies the function as a composable, making it easy to recognize in the code. See execution_table step 1 where 'useCounter' is defined.

What happens if we don't use the 'use' prefix?

Without the prefix, it is harder to tell if a function is a composable or a regular function, which can confuse developers. The naming convention in step 1 helps avoid this.

How does the reactive state 'count' update in the component?

The 'count' is a ref returned by the composable. When 'increment' is called (step 8), 'count.value' increases and Vue automatically updates the UI. See variable_tracker for count changes.

Visual Quiz - 3 Questions

Look at the execution_table step 6. What does calling useCounter() return?

A An object with reactive count and increment function

B A number representing the count

C A string with the name 'useCounter'

D Nothing, it just runs code

💡 Hint

Check the 'Result' column in step 6 of execution_table

At which step does the reactive count value increase?

A Step 3

B Step 5

C Step 8

D Step 2

💡 Hint

Look for when increment() is called in execution_table

If we rename 'useCounter' to 'counter', what is the main impact?

A No impact, code works the same

B It becomes harder to identify it as a composable

C It breaks the reactive state

D The increment function stops working

💡 Hint

Refer to key_moments about the importance of the 'use' prefix

Concept Snapshot

Composable functions in Vue should start with 'use' prefix.
This naming helps identify them as reusable reactive logic.
They return reactive state and functions.
Import and call them inside setup() of components.
Use returned reactive data in templates for automatic updates.

Full Transcript

This visual execution shows how to create and use a Vue composable function with the 'use' prefix. First, we define a function named 'useCounter' that creates a reactive count variable and an increment function. We export this composable. Then, in a Vue component, we import and call 'useCounter' inside the setup function to get reactive data. The count value is used in the template and updates automatically when increment is called. The 'use' prefix helps developers quickly recognize composables in code, improving clarity and maintainability.